29093 2015-08-27 16:27:26 +0000 Elements that are focusable but not in the tab order should probably not have tabindex by default 0 2018-02-04 09:22:01 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED MOVED https://html.spec.whatwg.org/#dom-tabindex P3 normal Unsorted 1 contributor ian annevk bzbarsky d denilsonsa mike contributor oldest_to_newest 122795 0 contributor 2015-08-27 16:27:26 +0000 Specification: https://html.spec.whatwg.org/multipage/interaction.html Multipage: https://html.spec.whatwg.org/multipage/#dom-tabindex Complete: https://html.spec.whatwg.org/#dom-tabindex Referrer: Comment: Elements that are focusable but not in the tab order should probably not have tabindex by default 0 Posted from: 98.110.194.132 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:42.0) Gecko/20100101 Firefox/42.0 122796 1 bzbarsky 2015-08-27 16:28:07 +0000 In particular, on Mac a bunch of form controls are focusable (in that you can click on them and they get focus) but can't be tabbed to by default. 125618 2 annevk 2016-03-24 17:49:24 +0000 The specification already allows for this right by defaulting according to platform conventions? 125619 3 d 2016-03-24 17:51:53 +0000 I don't think so. The spec pretty clearly states > 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. Boris is, I believe, asking that elements that are focusable but not in the tab order should have -1. 125621 4 bzbarsky 2016-03-24 17:57:22 +0000 That's correct. 125622 5 annevk 2016-03-24 18:29:18 +0000 I see, thank you. https://github.com/whatwg/html/pull/938 should fix this. 129073 6 annevk 2018-02-04 09:22:01 +0000 This is now https://github.com/whatwg/html/issues/1786.