- From: <bugzilla@jessica.w3.org>
- Date: Mon, 09 May 2011 23:02:54 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11956 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |NEEDSINFO --- Comment #12 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-05-09 23:02:52 UTC --- 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: Did Not Understand Request Change Description: no spec change Rationale: I still don't understand the problem here. If the problem is just that bug 10919 was resolved in a way that you disagree with, please reopen or escalate that bug as per comment 4. If the problem is that ARIA doesn't define what happens when the user focuses a focusable element with role=presentation, then that's a bug in ARIA, regardless of whether that combination is allowed or not. If the bug is that browsers don't do what ARIA says, then file the bugs with the browsers. Note that allowing a role on an element has no relationship with whether browsers will support that role on an element, so the "that is how it is implemented" part of comment 0 makes no sense. -- 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 Monday, 9 May 2011 23:02:56 UTC