23347 2013-09-24 22:32:29 +0000 Element.tabIndex default on non-natively-focusable elements should be undefined rather than -1 2016-04-22 18:16:36 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC All RESOLVED MOVED a11y, a11y_focus P2 editorial --- 1 jcraig chaals arronei chaals lwatson mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 93758 0 jcraig 2013-09-24 22:32:29 +0000 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." 93817 1 jcraig 2013-09-25 17:35:57 +0000 Might also need a change to the data type to support this distinction. Currently: "The tabindex attribute, if specified, must have a value that is a valid integer." 120947 2 chaals 2015-06-12 14:47:22 +0000 This looks like part of the mess that is focus management and keyboard interaction :( 125867 3 chaals 2016-04-14 22:28:10 +0000 Moved to Github: https://github.com/w3c/html/issues/199 Note that at least Firefox, Safari and Blink try to do what they are told, but have bugs. 126051 4 arronei 2016-04-22 18:16:36 +0000 HTML5.1 Bugzilla Bug Triage: Moved, this issue has been moved to the Github https://github.com/w3c/html/issues/199 If this resolution is not satisfactory, please copy the relevant bug details/proposal into the issue at the W3C HTML5 Issue tracker: https://github.com/w3c/html/issues/new where it will be re-triaged. Thanks!