- From: <bugzilla@jessica.w3.org>
- Date: Fri, 07 Mar 2014 17:51:53 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24972 Bug ID: 24972 Summary: menuitem as void element Product: HTML WG Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P2 Component: HTML5 spec Assignee: dave.null@w3.org Reporter: master.skywalker.88@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 Please consider removing <menuitem> from the list of void elements. It is a new element and its context is in a list of other menuitem elements. When it will be used (either thanks to a polyfill or after starting implementation) it isn't going to be backward compatible, as browsers fail to interpret it as void element and end up nesting subsequent menuitems. So instead of having <menu> + <menuitem></menuitem> + <menuitem></menuitem> + <menuitem></menuitem> </menu> user agents will interpret <menu> + <menuitem> + <menuitem> + <menuitem></menuitem> </menuitem> </menuitem> </menu> Moreover, this structure would allow authors to specify the text of the command inside the element itself, rather than as attribute. It could be suggested as alternative, in a manner similar to <option> tag. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 7 March 2014 17:51:54 UTC