Side navigation
#5701 closed bug (fixed)
Opened December 22, 2009 07:51PM UTC
Closed December 22, 2009 08:04PM UTC
Last modified March 15, 2012 10:39AM UTC
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: |
Description
Attachments (0)
Change History (6)
Changed December 22, 2009 08:04PM UTC by comment:1
| resolution: | → fixed |
|---|---|
| status: | new → closed |
Changed December 31, 2009 05:56AM UTC by comment:2
| version: | 1.4a2 → 1.4a3 |
|---|
Changed December 31, 2009 05:57AM UTC by comment:3
| version: | 1.4a3 → 1.4a2 |
|---|
Changed February 15, 2011 09:47AM UTC by comment:4
Sorry by relive this ticket... But where is the sense on:
parent.parentNode.selectedIndex;?
For me and Closure Compiler don't make sense! :S
Changed February 15, 2011 01:44PM UTC by comment:5
Replying to [comment:4 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 ??
Changed February 16, 2011 04:38AM UTC by comment:6
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?
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.