- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 07 Jan 2010 12:01:53 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8674 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-01-07 12:01:52 --- 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: We can't change the default, since that would break back-compat. As far as I can tell, the suggested type=popup is exactly what a <menu> nested in a type=toolbar <menu> would do per spec today: <menu> <menu type=toolbar label="..."> ... </menu> </menu> Originally IIRC you could do what you describe — basically one of the options was that <menu> would turn into a button. However, it's not clear that that kind of UI is actually something we want to encourage outside of a toolbar, which is why it ended up being made just a feature of the toolbar (much like how submenus are a feature of a context menu). -- 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 Thursday, 7 January 2010 12:01:54 UTC