- From: <bugzilla@jessica.w3.org>
- Date: Sat, 05 Apr 2014 14:48:49 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25135 steve faulkner <faulkner.steve@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #9 from steve faulkner <faulkner.steve@gmail.com> --- EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: partially accepted Change Description: added constraint to conforming usage of button on summary see commit https://github.com/w3c/html/commit/541825211eece40c2ef139fb5305e6601c436ad8 Rationale: agreed with commenter that if the summary element contains interactive content the role=button does not make sense. While by default summary is not classed as interactive content, as it states in the spec "The tabindex attribute can also make any element into interactive content." http://www.w3.org/html/wg/drafts/html/master/dom.html#interactive-content-0 In the case where tabindex is used on summary to make it interactive a role=button is allowed unless the summary contains interactive descendant elements. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Saturday, 5 April 2014 14:48:50 UTC