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

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

From: David Hyatt <hyatt@apple.com>
Date: Wed, 7 Dec 2005 16:06:39 -0800
Message-ID: <5F826709-884E-4BC9-A237-58B2FF20401F@apple.com>
Shipping Safari actually supports <hr> as separators in <select>  
dropdowns now.  We needed this for Dashboard widgets that wanted to  
be able to put separators into their select UI.

dave

On Dec 7, 2005, at 4:00 PM, Ian Hickson wrote:

>
>
>> Then again, toolbars often have separators, so maybe they're a  
>> type of
>> list anyways and require <li>-type markup, thus making <menu type>  
>> more
>> appropriate. Hmm...
>
> <hr> is our separator element. Not sure what it stands for exactly.  
> "Here
> is a separatoR", maybe. *cough*
>
>
>> Above, the type "menu" is assumed to be a sort of context menu  
>> activated
>> either by a true context menu feature or by a <menulabel>. Then  
>> again,
>> <commandbar>-type elements are flat, and while they may have
>> groupings/separators (for toolbars, at least), they don't have
>> multilevel groupings.
>
> They kind of do, in some contexts, e.g. drop-down buttons.
>
> -- 
> Ian Hickson               U+1047E                ) 
> \._.,--....,'``.    fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   _ 
> \  ;`._ ,.
> Things that are impossible just take longer.   `._.-(,_..'-- 
> (,_..'`-.;.'
Received on Wednesday, 7 December 2005 16:06:39 UTC

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