Ticket #11568 (closed bug: duplicate)
unreliable behaviour with selecting tabIndex with attributes selectors
|Reported by:||felash@…||Owned by:|
I found that using [tabIndex] or [tabIndex=0] or [tabIndex='0'] as selectors yield unreliable results.
I made a jsfiddle there : http://jsfiddle.net/RRktv/2/
As I understand, using [tabIndex=0] triggers the Sizzle search, where as the other forms trigger using querySelectorAll if available. Therefore, you can use IE7 or IE8/9 in IE7 mode to always use the Sizzle search.
This is especially problematic in IE6/7 because then we can't get those nodes with the tabIndex attribute especially set.
Also, this means the result for this selector is not consistent across browsers AND across two valid but different invocations in the same browser (ie tabIndex=0 and tabIndex='0')
Therefore, I think it should be fixed earlier than what you're suggesting in ticket #8473.
- Priority changed from undecided to low
- Component changed from unfiled to selector
- Status changed from new to open
- Milestone changed from None to 1.next
- Status changed from open to closed
- Resolution set to duplicate