[whatwg] Menus, fallback, and backwards compatibility: ideas wanted
nheagy at point2.com
Wed Dec 7 14:59:09 PST 2005
> menu n. A list of available options.
If the definition of menu is too vague then couldn't we include <ul> and
<ol>? Especially since people make dynamic menus with these right now.
However, imho ideally the menubar would be powerful enough to turn into
something like MS Office 12's ribbon. When I consider how that might
look in html I think that ultaflexible menus within menus would work
From: whatwg-bounces at lists.whatwg.org
[mailto:whatwg-bounces at lists.whatwg.org] On Behalf Of Ian Hickson
Sent: December 7, 2005 4:17 PM
To: Matthew Raymond
Cc: whatwg at whatwg.org; Lachlan Hunt
Subject: Re: [whatwg] Menus, fallback, and backwards compatibility:
On Fri, 2 Dec 2005, Matthew Raymond wrote:
> That's not a menu. It's a MENUBAR.
What's the difference?
I would argue that the following are all the same:
* pull-down menus
* drop-down menus
* context menus
They're just different presentations of the same underlying concept:
lists of commands or options.
menu n. A list of available options.
This is why I think it makes sense to use one menu to describe all of
Now, there is a small difference between context menus and the others in
the list above in that context menus are irrelevant until activated on
specific items, so we need a way to mark them. There's also a practical
difference between <menu> as implemented today and <menu> as we want it
work (with natively implemented dynamic UI), so we need a way to mark
those too. This is why I was thinking of an attribute on <menu>.
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
More information about the whatwg