- From: <chaals@yandex-team.ru>
- Date: Sat, 14 Mar 2015 03:28:46 +0300
- To: HTML Accessibility Task Force <public-html-a11y@w3.org>
related to the keyboard stuff. So I updated that a bit -------- Beginning of forwarded message -------- 14.03.2015, 01:19, "bugzilla@jessica.w3.org" <bugzilla@jessica.w3.org>: https://www.w3.org/Bugs/Public/show_bug.cgi?id=28212 Bug ID: 28212 Summary: Making an element with tabindex attribute to be an interactive content breaks backward compatibility Product: HTML WG Version: unspecified Hardware: PC URL: https://html.spec.whatwg.org/multipage/dom.html#intera ctive-content-2 OS: All Status: NEW Severity: normal Priority: P2 Component: HTML5 spec Assignee: dave.null@w3.org Reporter: arai.unmht@gmail.com QA Contact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-admin@w3.org, public-html-wg-issue-tracking@w3.org Created attachment 1584 --> https://www.w3.org/Bugs/Public/attachment.cgi?id=1584&action=edit 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? -- You are receiving this mail because: You are on the CC list for the bug. -------- End of forwarded message -------- -- Charles McCathie Nevile - web standards - CTO Office, Yandex chaals@yandex-team.ru - - - Find more at http://yandex.com
Received on Saturday, 14 March 2015 00:29:16 UTC