- From: <bugzilla@jessica.w3.org>
- Date: Tue, 07 Sep 2010 16:55:23 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10479 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WONTFIX --- Comment #6 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-09-07 16:55:23 --- 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: Rejected Change Description: no spec change Rationale: If you changed the role of a <details> element, the user could no longer expand the <details> element to get to its contents. That would be a net loss of accessibility. If you have a group of radio buttons inside a <details> and you need to wrap them with role=radiogroup, then you should use an element for that group; <details> is not it. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Tuesday, 7 September 2010 16:55:25 UTC