W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2007

[whatwg] Looking at menus in HTML5...

From: Křištof Želechovski <giecrilj@stegny.2a.pl>
Date: Wed, 8 Aug 2007 19:38:17 +0200
Message-ID: <001601c7d9e2$ebae8d70$4d01010a@IBM42F76C011DF>
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 &#9096;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

-----Original Message-----
From: whatwg-bounces@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@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.
Received on Wednesday, 8 August 2007 10:38:17 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:36 UTC