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

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

From: Anne van Kesteren <fora@annevankesteren.nl>
Date: Sat, 03 Dec 2005 13:21:39 +0100
Message-ID: <20051203132139.iq1yhk0jqvtwsogw@webmail.annevankesteren.nl>
Quoting Matthew Raymond <mattraymond at earthlink.net>:
> Without fallback, this would be the following:
>
> | <menulabel for="foo">Menu Label</menulabel>
> |
> | <cmd id="foo">
> |  <option>Item 1
> |  <option>Item 2
> |  <option>Item 3
> | </cmd>

Too much markup imho. Especially for the one with fallback.


>  As you can see, <menu> uses the |list| attribute from Web Forms 2.0
> to load data from a <datalist>. Since <menulabel> is associated with a
> <menu> element, there's no change in its semantics. With the exception
> of the <button> element, the use of <datalist> is pretty much how it is
> used in WF2.

Even more markup...


> We're running into too many possible sources for adding labels. If
> you include this we have:
>
> * A child <option>.
> * The first <option> in the child <select>.
> * A child text node.
> * A child <label> node.
> * A child <button>.

Not sure what you mean. My suggestion was to take the first Node from the
NodeList when calling getElementsByTagNameNS method with the parameters
"http://www.w3.org/1999/xhtml" and "option" from the <cmd> element and give
that element "semantic meaning". (Which is essentially what is done 
today so it
is quite backwards compatible.)


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
Received on Saturday, 3 December 2005 04:21:39 UTC

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