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

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

From: Ian Hickson <ian@hixie.ch>
Date: Wed, 7 Dec 2005 00:29:44 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0512070015370.17886@dhalsim.dreamhost.com>
On Tue, 29 Nov 2005, Matthew Raymond wrote:
>
> Well, what I don't like about this scenario is that we end up with a lot 
> of different markup in <menu>:
> 
> | <menu>
> |   <a/>
> |   <cmd/>
> |   <command/>
> |   <li/>
> |   <menulabel/>
> |   <menu label=""/>
> | </menu>

So the situation would be:

   <menu x="y">
    <li> Z </li>
    <li> Z </li>
    <li> Z </li>
   </menu>

...or:

   <menu x="y">
    Z
    Z
    Z
   </menu>

...where "Z" is one of the following:

   <command>
   <a>
   <button>
   <input> [1]
   <menu>
   <select> <option> </select> [2]

[1] assuming type="" is one of radio, checkbox, button, submit, reset, 
    move-up, move-down, add, or remove.
[2] (optionally with a <button/>, <input/>, or <label/> element)

...and all other content is ignored (and could be used for fallback).

Not quite sure how to get the label for nested <menu> elements yet.

Also not quite sure how to make all this styleable, especially for the 
toolbar type of <menu>. Although... maybe with XBL2's xbl:pseudo="" stuff 
we can make use of that. Hmm.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 6 December 2005 16:29:44 UTC

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