28212 2015-03-13 22:18:37 +0000 Making an element with tabindex attribute to be an interactive content breaks backward compatibility 2015-06-19 15:01:29 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC All RESOLVED INVALID https://html.spec.whatwg.org/multipage/dom.html#interactive-content-2 a11ytf, a11y_focus P0 normal --- 1 arai.unmht faulkner.steve chaals mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 118595 0 1584 arai.unmht 2015-03-13 22:18:37 +0000 Created attachment 1584 demo for tabindex, label, and input Originally reported here: https://bugzilla.mozilla.org/show_bug.cgi?id=1141455 https://bugzilla.mozilla.org/show_bug.cgi?id=1135374 In the attached demo (copied from http://jsbin.com/budisehuyo/3/ ), what the spec says is that clicking on the span element should not turn on/off the checkbox, right? https://html.spec.whatwg.org/multipage/forms.html#the-label-element:the-label-element-10 > The activation behaviour of a label element for events targeted at interactive > content descendants of a label element, and any descendants of those > interactive content descendants, must be to do nothing. https://html.spec.whatwg.org/multipage/dom.html#interactive-content-2 > Interactive content is content that is specifically intended for user > interaction. > The tabindex attribute can also make any element into interactive content. Now it's implemented in Firefox Developers Edition 38.0a2 (2015-03-13) and Firefox Nightly 39.0a1 (2015-03-13). But the behavior is different from previous versions and other browsers, and it causes compatibility problem in capitainetrain.com (see https://bugzilla.mozilla.org/show_bug.cgi?id=1135374 ). Could we remove "The tabindex attribute can also make any element into interactive content." from 3.2.4.2.7, or add some restriction to make it backward compatible? 118596 1 chaals 2015-03-14 00:24:47 +0000 Also added to where I am tracking tabindex stuff as part of fixing focus navigation / activation shortcuts, etc. https://www.w3.org/WAI/PF/HTML/wiki/Tabindex 121036 2 mike 2015-06-16 10:11:11 +0000 Agree that it would be good to have a spec change here, and raising priority after reviewing implementer feedback. 121235 3 chaals 2015-06-19 15:00:25 +0000 The spec makes sense, and capitainetrain.com shouldn't have nested interactive elements. What they have done is analagous to having <label> <a href="#">you can't do <a href="http://w3cmemes.tumblr.com">THIS</a> without expecting problems. </a> </label> I propose closing this as invalid 121236 4 chaals 2015-06-19 15:01:29 +0000 The tabindex should be applied to the label, or the input, which are already interactive elements. 1584 2015-03-13 22:18:37 +0000 2015-03-13 22:18:37 +0000 demo for tabindex, label, and input demo.html text/html 708 arai.unmht PCFET0NUWVBFIGh0bWw+CjxodG1sPgo8aGVhZD4KICA8bWV0YSBjaGFyc2V0PSJ1dGYtOCI+CiAg PHRpdGxlPkpTIEJpbjwvdGl0bGU+CjxzdHlsZSB0eXBlPSJ0ZXh0L2NzcyI+CmxhYmVsIHsKICBi YWNrZ3JvdW5kOiByZ2JhKDAsIDAsIDI1NSwgMC4yKTsKICBib3JkZXI6IDFweCBzb2xpZCBibHVl Owp9Ci5jaGVja2JveC1jb250YWluZXIgewogIGJhY2tncm91bmQ6IHJnYmEoMCwgMCwgMjU1LCAw LjQpOwogIHBhZGRpbmctbGVmdDogMjBweDsKICBwYWRkaW5nLXJpZ2h0OiAyMHB4Owp9Cjwvc3R5 bGU+CjwvaGVhZD4KPGJvZHk+CiAgPHA+VGFiaW5kZXggY2F1c2VzIGlucHV0IHRvIG1pc3MgY2xp Y2sgZXZlbnRzLjwvcD4KICA8dWw+CiAgICA8bGk+QSBjbGljayBvbiB0aGUgY2hlY2tib3ggc2Vs ZWN0IHRoZSBjaGVja2JveDwvbGk+CiAgICA8bGk+QSBjbGljayBvbiB0aGUgbGlnaHQtYmx1ZSBs YWJlbCBzZWxlY3RzIHRoZSBjaGVja2JveDwvbGk+CiAgICA8bGk+QSBjbGljayBvbiB0aGUgZGFy ay1ibHVlIGFyZWEgZG9lc24ndCBzZWxlY3QgdGhlIGNoZWNrYm94LjwvbGk+CiAgPC91bD4KICA8 bGFiZWw+CiAgICA8c3BhbiBjbGFzcz0iY2hlY2tib3gtY29udGFpbmVyIiB0YWJpbmRleD0iMSI+ CiAgICAgIDxpbnB1dCB0eXBlPSJjaGVja2JveCIvPgogICAgPC9zcGFuPgogICAgTGFiZWwKICA8 L2xhYmVsPgo8L2JvZHk+CjwvaHRtbD4K