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: Tue, 6 Dec 2005 21:52:56 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0512062148290.17886@dhalsim.dreamhost.com>
On Tue, 29 Nov 2005, Lachlan Hunt wrote:
>
> Couldn't the for attribute used to associate> the button with the the 
> select, be used to determine how to render the controls without the 
> menu/menubar/etc. wrapper?

Making one element render or not render according to an attribute on 
another element is not really workable (especially in the face of dynamic 
changes). It makes good sense semantically, but it would be a pain to 
implement sanely.


> > It's unfortunate about the button being first, too.
> 
> From an implementation perspective, is there any reason why it couldn't 
> work with the order of the button and select elements swapped?  At the 
> moment, I thinking it should work if the button and select are just 
> immediate siblings of each other in any order, though I'm not sure if it 
> should work if there were other content in between.

Right, that's what I meant when I wrote:

> > I guess we could change that if we say that in the new world in an <li> any
> > <select>s are ignored and just the <button> is looked for... Hmm.
> 
> I'm not sure I understand.  Wouldn't that break many existing documents 
> which do have select and buttons inside li elements?

I only meant inside <menubar>.

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

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