W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2007

[whatwg] Looking at menus in HTML5...

From: Ian Hickson <ian@hixie.ch>
Date: Mon, 6 Aug 2007 23:35:50 +0000 (UTC)
Message-ID: <Pine.LNX.4.64.0708062322020.9753@dhalsim.dreamhost.com>
On Tue, 5 Dec 2006, Matthew Raymond wrote:
>
> Any |label|-free <menu> elements that are immediate children of a <menu 
> type="popup"> or <menu type="toolbar"> should be ignored. A menu within 
> a menu shouldn't be used for anything but a submenu. If we want true 
> command groups, we need a new element, perhaps named "cmdgroup" or 
> something. (Is there a sufficient use case for non-hierarchical groups 
> that produce separators? Or is <hr> sufficient? Note that <hr> degrades 
> to a visible form on legacy user agents.)

I don't understand why? It seems sensible to me to use <menu> for 
grouping.


> I'm not sure the spec says this or not, but any <menu> that is the 
> descendant of a <menu type="popup"> or <menu type="toolbar"> element 
> should be ignored if it has an explicit |type| attribute value of "list" 
> or "toolbar". Toolbars and popups should only contain popup submenus, so 
> anything that isn't <menu> (with no |type|) or <menu type="popup"> 
> should be ignored.

This seems like it would just complicate things with no advantage.


> Is there a ways to set an <option> or <li> element as default item? I'll 
> have to check the spec again, but I believe some features are 
> specifically reserved for <command>...

Right, some of the features only work with <command> right now.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 6 August 2007 16:35:50 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:36 UTC