Quoting Lachlan Hunt <[EMAIL PROTECTED]>:
My point is that this command menu is basically made up of a label, a
select control and a button, and that we already have a <label>
element for associating with select elements. Therefore, we don't
need to use another type of label element for that. <menulabel> is
fine for navigational menus.
That would also require a <form> element around the command menu. 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>
Now assuming scripting is more or less required for applications this can be
perfectly backwards compatible. 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.
Cheers,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
