In IE9rc *[tabIndex] select all elements without tabindex also

[EMVI]

The live events are triggert for all elements, if I remove the "*[tabIndex]" selector the events are only triggert for a and :input elements.

$('a,:input,*[tabIndex]')
    .live('focus',function(){
        this.isFocused = true;
    })
    .live('blur',function(){
        this.isFocused = false;
    })
    .live('mousedown',function(){
        // in webkit some input doesn't get focus on select by mousedown
        if( !this.isFocused ){
            this.focus();
        }
    });

[addyosmani]

Thanks for submitting a ticket to the jQuery Bug tracker. Could you please provide us a complete reduced test-case on jsFiddle.net that we can run to evaluate whether this issue is due to jQuery core or a bug in your implementation?

[EMVI]

Here is the jsFiddle test-case: ​http://jsfiddle.net/mnqBT/3/

[dmethvin]

In IE6/7 there's no querySelectorAll and the Sizzle JS engine path is looking at the tabIndex property (which exists on all elements) rather than an explicit attribute.

[john]

Confirmed in bug triage.

[Timmy Willison]

Moving to 1.8. After hooking up Sizzle to jQuery.attr, everything works as we intended. One of the ways we intend it to work, however, prohibits us from fixing this bug until we can deprecate retrieving the tabIndex property with .attr('tabindex'). We currently copy over the propHook to attrHooks in order to mirror previous behavior. When we do deprecate this, it will fix this selector bug and put attr even closer to what it should be, but we will see users complain about getting undefined instead of a number when we do deprecate the tabindex attrHook. I'd like to officially deprecate it in 1.7 and remove it in 1.8 effectively killing this bug. Any objections?

[Timmy Willison]

#11568 is a duplicate of this ticket.

[Timmy Willison]

Remove the tabindex attrHook. Fixes #8473

Changeset: 3e2a77c5e882b5fc88bf5469ea00067833a2a059