[whatwg] Looking at menus in HTML5...

[Andrew Fedoniouk]

----- Original Message ----- 
From: "Křištof Želechovski" <giecrilj at stegny.2a.pl>
To: "'Andrew Fedoniouk'" <news at terrainformatica.com>; "'Ian Hickson'" 
<ian at hixie.ch>
Cc: "'WHAT WG List'" <whatwg at whatwg.org>
Sent: Wednesday, August 08, 2007 10:38 AM
Subject: Re: [whatwg] Looking at menus in HTML5...


> First of all, your example renders as CopyCtrl-C so you really need a quad
> space in between.
> Second, using a typewriter font in a menu is a bad idea because it is 
> wider
> than ordinary text and it attracts more attention than the menu label
> itself, which is an evident annoyance.  If you really have to, use ^C or
> instead-or ⎈C, except that nobody really understands the latter sign
> in spite of what the Unicode standard says and Microsoft Windows renders 
> it
> as a square (glyph missing).
> Happy coding,
> Chris

I would insist that following

<menu type="context-menu">
  <li>Copy<kbd>Ctrl-C</kbd></li>
</menu>

1) is semantically correct construction as "KBD: Indicates text to be 
entered by the user." [1]
2) with proper styling like: http://terrainformatica.com/w3/context-menu.jpg 
it has better
usabilty quality than just a plain text.

Andrew Fedoniouk.
http://terrainformatica.com

[1] http://www.w3.org/TR/html401/struct/text.html#edef-KBD



>
> -----Original Message-----
> From: whatwg-bounces at lists.whatwg.org
> [mailto:whatwg-bounces at lists.whatwg.org] On Behalf Of Andrew Fedoniouk
> Sent: Wednesday, August 08, 2007 4:11 AM
> To: Ian Hickson
> Cc: WHAT WG List
> Subject: Re: [whatwg] Looking at menus in HTML5...
>
>
> ----- Original Message ----- 
> From: "Ian Hickson" <ian at hixie.ch>
> To: "Andrew Fedoniouk" <news at terrainformatica.com>
> Cc: "WHAT WG List" <whatwg at whatwg.org>
> Sent: Tuesday, August 07, 2007 1:52 PM
> Subject: Re: [whatwg] Looking at menus in HTML5...
>
>
>> On Tue, 7 Aug 2007, Andrew Fedoniouk wrote:
>>>
>>> Pure text? Why?
>>
>> With HTML5 we're following a design principle of not biting off more than
>> we can chew at once -- so the initial design is intended to be very
>> conservative.
>>
>
> I think that
>
> <menu type="context-menu">
>   <li>Copy<kbd>Ctrl-C</kbd></li>
> </menu>
>
> is conservative enough as it allows me to define typical menus.
>
> All modern UAs have their own implementation of menus
> so they already can "chew" menu items with markup and styling.
>
> Otherwise <menu> should not use <li> but <option> or so.
> But this will not be backward compatible.
>
>
>
>