[whatwg] Menus, fallback, and backwards compatibility: ideas wanted
Nate H.
whatwg at heagy.com
Wed Dec 14 14:24:53 PST 2005
Not too ugly, just a little bit ugly. Would this be able to handle
menus within menus? I'm guessing nesting a <select> within another
<select> will break current UAs.
N
> <form action="redirect.cgi">
> <menu type="commands">
> <menu label="Select site...">
> <select name="goto"
> onchange="if (this.options[this.selectedIndex].value)
> location = this.options[this.selectedIndex].value">
> <option value="" selected="selected"> Select site: </option>
> <option value="http://www.apple.com/"> Apple </option>
> <option value="http://www.mozilla.org/"> Mozilla </option>
> <option value="http://www.opera.com/"> Opera </option>
> </select>
> <span><input type="submit" value="Go"></span>
> </menu>
> </menu>
> </form>
>
> The outer menu makes the toolbar, the inner menu is a drop-down button on
> that toolbar. (Well, semantically it's just saying that there's a set of
> commands, consisting of a nested set of commands, which allows things like
> the Ribbon effect for expanding and/or contracting the UI on the fly.)
>
> The <span></span> hides the <input> from the <menu>. The value="" hides
> that <option> from the menu.
>
> Is this too ugly?
>
> --
> Ian Hickson U+1047E )\._.,--....,'``. fL
> http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
> Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
>
--
Nate
-------
heagy.com
More information about the whatwg
mailing list