- From: <bugzilla@jessica.w3.org>
- Date: Tue, 22 Nov 2011 10:23:52 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13608 --- Comment #26 from Jan Varga <jan.varga@gmail.com> 2011-11-22 10:23:51 UTC --- (In reply to comment #24) > It's not "extended" syntax. That's the point. It's the existing features of > HTML, like <a>, <button>, <select>, etc, used for their existing semantics, in > a way that can have graceful degradation in legacy UAs, and defined in such a > way that they all expose a uniform front and can therefore be used to display a > consistent UI either in context menus or in toolbars. > > Creating a new element for this is just unnecessary. (<command> itself is > unnecessary here, but is interesting because it later will allow us to create > commands that are defined once but exposed in multiple places via reference.) Ok, so my personal opinion is what I already mentioned. If we add support for <a>, <button>, <select>, etc, then <menuitem> is useless. Otherwise <menuitem> is much easier to use. So the question is, do we want to support existing elements ? It seems that implementation in webkit got lower prioritty, they are not actively working on 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, 22 November 2011 10:23:58 UTC