- From: <bugzilla@jessica.w3.org>
- Date: Sat, 19 May 2012 08:45:52 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17115 Summary: The first example of the menu element is about how to markup a menubar in HTML. For the markup a menu in the toolbar state was used. However, the section about native ARIA semantics describes that it's not possible to change the semantics of a menu in the Product: HTML WG Version: unspecified Platform: Other URL: http://www.whatwg.org/specs/web-apps/current-work/#top OS/Version: other Status: NEW Severity: normal Priority: P3 Component: HTML5 spec (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: contributor@whatwg.org QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org Specification: Multipage: http://www.whatwg.org/C#top Complete: http://www.whatwg.org/c#top Comment: The first example of the menu element is about how to markup a menubar in HTML. For the markup a menu in the toolbar state was used. However, the section about native ARIA semantics describes that it's not possible to change the semantics of a menu in the toolbar state to menubar. So the menu element example used a menu in toolbar state to mark up a menubar. But then you're not allowed to set the right semantics. Maybe you could introduce a menubar state of the menu element or just allow the use of ARIA's menubar role on the menu element. Posted from: 178.191.165.211 User agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.168 Safari/535.19 Comodo_Dragon/18.3.0.0 -- Configure bugmail: https://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 Saturday, 19 May 2012 08:45:56 UTC