[Bug 23347] New: Element.tabIndex default on non-natively-focusable elements should be undefined rather than -1

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23347

            Bug ID: 23347
           Summary: Element.tabIndex default on non-natively-focusable
                    elements should be undefined rather than -1
           Product: HTML WG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec
          Assignee: dave.null@w3.org
          Reporter: jcraig@apple.com
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-admin@w3.org,
                    public-html-wg-issue-tracking@w3.org

This sentence is not accurate. For example, if you set an explicit
tabindex="-1" on a SPAN element, it is not user-focusable in sequential tab
order, but it is user-focusable if clicked with a mouse. As such, there is a
difference between Element.tabIndex being equal to -1, and Element.tabIndex
being undefined, and the reflected DOM attribute defaults should account for
that.


http://www.w3.org/html/wg/drafts/html/master/single-page.html#attr-tabindex

"The tabIndex IDL attribute must reflect the value of the tabindex content
attribute. Its default value is 0 for elements that are focusable and −1 for
elements that are not focusable."


Suggested change: (changed "-1" to "undefined")

"The tabIndex IDL attribute must reflect the value of the tabindex content
attribute. Its default value is 0 for elements that are focusable and undefined
for elements that are not focusable."

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Tuesday, 24 September 2013 22:32:31 UTC