W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2005

[whatwg] Menus, fallback, and backwards compatibility: ideas wanted

From: Matthew Raymond <mattraymond@earthlink.net>
Date: Wed, 14 Dec 2005 17:45:55 -0500
Message-ID: <43A0A0A3.80302@earthlink.net>
Nate H. wrote:
>>   First of all, my suggestion is that submenus always have an
>>associated <menulabel>.
> 
> I've taken <menulabel> to be a text label specifically and wonder
> about menus opened from an icon-only, such as would be found on a
> toolbar.

   I think it's up to the user agent to decide what to do with the
contents of a <menulabel>. Since <menulabel> is a new element, we can
always add the <command> element's |icon| attribute from the current
spec, or allow the use of <img> and other markup within <menulabel>.
That seems to be a step ahead of what we're discussing at the moment,
though. Right now, we're just trying to figure out general menu markup
structure.

   Also, keep in mind that the user agent should be free to ignore some
attributes/elements if the platform of the user agent doesn't support
the features they use. An example would be a device that can't display
images inside menus. As a result, it's better to provide a wide array of
"should" features in markup than give the web authors too few options.
Received on Wednesday, 14 December 2005 14:45:55 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:44 UTC