[whatwg] Menus, fallback, and backwards compatibility: ideas wanted
Matthew Raymond
mattraymond at earthlink.net
Fri Dec 2 08:51:40 PST 2005
Lachlan Hunt wrote:
> Anne van Kesteren wrote:
>>I wonder if there always is a <form> element. There was also this suggestion:
>>
>># <select>
>># <option label>Action ...
>># <option>Select All
>># <option>Deselect All
>># <option>Archive Selected
>># </select>
>
>
> That's an interesting idea, and kind of fits with the existing abuse of
> the first option as a label, rather than an actual option, as in:
>
> <select>
> <option>Please Select
> <option>foo
> </select>
First, I don't like the idea of abuse of legacy markup any more than
I like abuse of current markup. Second, <option> already has a |label|
attribute.
>>Perhaps put some additional container element around it and make <select>
>>optional for fallback (same as with <datalist>) and you have some kind of
>>solution.
>
> Do you mean like this:
>
> <cmd>
> <option>foo
> <option>bar
> </cmd>
>
> would be the same as:
>
> <cmd>
> <select>
> <option>foo
> <option>bar
> </select>
> <button/>
> </cmd>
>
> Since the first would only be supported by new UAs with no good
> fallback, the button would be completely unnecessary.
So we've completely reinvented <menu><select/></menu>, only using
<cmd> as the parent instead. Why not just return to using
<menu><select/></menu> then?
| <menu>
| <select>
| <option>foo
| <option>bar
| </select>
| <button/>
| </menu>
More information about the whatwg
mailing list