W3C home > Mailing lists > Public > public-html@w3.org > August 2008

Re: Detailed review of 3.18.3. The command and 3.18.4. the menu elements

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 5 Aug 2008 21:58:02 +0000 (UTC)
To: Mihai Sucan <mihai.sucan@gmail.com>
Cc: public-html <public-html@w3.org>
Message-ID: <Pine.LNX.4.62.0808052120580.5140@hixie.dreamhostps.com>

On Wed, 12 Sep 2007, Mihai Sucan wrote:
>
> 1. [issue mentioning irrelevant="", which I will deal with later]
> 
> 2. [agreement with issue notes in the draft, will be dealt with later]
>
> I do not agree with the current spec definition of the click() method. I 
> want to be able to fire a synthetic click event at the element, and have 
> it work like the click() method does. There's absolutely no reason to 
> overly complicate things.

This would require changes to the DOM specs, really, to say that elements 
can have default behaviours invoked even when they don't fire the events 
themselves... it doesn't really match the concept of how events work.


> 3. I don't think having commands where metadata elements are expected is 
> correct.
> 
> Commands are not metadata elements.

The idea (not yet executed in the spec) is for <command> elements to 
define a command that can then be referred to from elsewhere, so we want 
it to be possible to just put them in the <head>.


> 1. [typo, already fixed]
> 
> 2. I'd like to better understand the autosubmit attribute [5], defined 
> for the menu element.
> 
> Why was it defined? What are the use-cases for having a menu which 
> automatically submits the form when the user changes input 
> type=checkbox|radio?

I've removed it.


> 3. In the section 3.18.4.3. "Context menus" [6] I cannot find any 
> mention about this scenario:
> 
> <menu id="myMenu">
>  <command ...>...</command>
>  <command contextmenu="myMenu2" ...>...</command>
>  <command ...>...</command>
> </menu>
> 
> <menu id="myMenu2">
> ...
> </menu>
> 
> <p contextmenu="myMenu">Right-click this!</p>
> 
> This scenario "nests" context menus. For now, I don't know any software 
> application which allows to right-click on a context menu for a "second 
> level" context menu, but that's not impossible.
> 
> Should the spec disallow the usage of the contextmenu attribute within 
> context menus?

I don't think disallowing it would be especially necessary. While it's bad 
UI, if UAs want to support it, why shouldn't it work? Maybe we should 
revisit this once UAs have it implemented, and see if it makes sense to 
disallow it.


> Also, how about this:
> 
> <menu id="myMenu" contextmenu="myMenu">
> ...
> </menu>
> 
> or ...
> 
> <menu id="myMenu">
> <command ...>...</command>
> <command contextmenu="myMenu" ...>...</command>
> <command ...>...</command>
> </menu>
> 
> How should UAs deal with these cases?

There doesn't seem anything especially difficult about these.


> The following section 3.18.5. "Commands" [7]:
> 
> 1. [irrelevant interaction, will be dealt with later]

Thanks for the feedback,
-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 5 August 2008 21:58:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:21 GMT