Bug Tracker

Opened 10 years ago

Closed 10 years ago

Last modified 8 years ago

#5701 closed bug (fixed)

Make Sure selected Works in Safari with Optgroup

Reported by: john Owned by:
Priority: major Milestone: 1.4
Component: core Version: 1.4a2
Keywords: Cc:
Blocked by: Blocking:

Change History (6)

comment:1 Changed 10 years ago by john

Resolution: fixed
Status: newclosed

Fixed. http://github.com/jquery/jquery/commit/4729f4d44326fd302c63af8f3324b6c4bac54084

I figure that the nodeNames could've been checked but that'd just be extra overhead - as it is there's no negative side-effects to accessing the selectedIndex property on an incorrect element.

comment:2 Changed 10 years ago by john

Version: 1.4a21.4a3

comment:3 Changed 10 years ago by john

Version: 1.4a31.4a2

comment:4 Changed 9 years ago by anonymous

Sorry by relive this ticket... But where is the sense on: parent.parentNode.selectedIndex;? For me and Closure Compiler don't make sense! :S

comment:5 in reply to:  4 Changed 9 years ago by jitter

Replying to anonymous:

Sorry by relive this ticket... But where is the sense on: parent.parentNode.selectedIndex;? For me and Closure Compiler don't make sense! :S

What are you trying to say? If you have anything useful to add please leave more then half a sentence.

btw. jQuery doesn't use Closure compiler so ??

comment:6 Changed 9 years ago by anonymous

On sure, I think that is a workaround on Safari. [parent.parentNode.selectedIndex] is a property (not function!). See a part of jQuery commented: http://jsfiddle.net/VFMQ2/ You get now?

Note: See TracTickets for help on using tickets.