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
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 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" <[EMAIL PROTECTED]> To: "Andrew Fedoniouk" <[EMAIL PROTECTED]> Cc: "WHAT WG List" <[EMAIL PROTECTED]> 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.
