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

Re: linking other elements to a "command"

From: Ian Hickson <ian@hixie.ch>
Date: Sat, 1 Aug 2009 09:30:14 +0000 (UTC)
To: "Hallvord R. M. Steen" <hallvord@opera.com>
Cc: public-html@w3.org
Message-ID: <Pine.LNX.4.62.0908010928150.6420@hixie.dreamhostps.com>
On Wed, 22 Jul 2009, Hallvord R. M. Steen wrote:
> the text about the "command concept" here: 
> http://www.whatwg.org/specs/web-apps/current-work/multipage/interactive-elements.html#concept-command
> states: "Once a command is defined, other parts of the interface can 
> refer to the same command".
> On reading that, I thought the spec intended to allow several 
> buttons/links/interactive features in a page to refer back to one 
> command (thus "inherit" that command's disabled/checked/hidden states to 
> the extent they would make sense for that element).
> The spec doesn't actually seem to enable this though. If I do 
> <menu><command id="c" onclick="foo()" title="Do foo 
> action"></command></menu> and want a <button> elsewhere to represent 
> that command, how do I link the <button> element to the <command>? Did I 
> misunderstand the concept?

Oops, that text should have been commented out. It is referring to the 
command="" attribute that I specced out but removed from the first 
version. I imagine we'll introduce it in a future version of the language.

Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Saturday, 1 August 2009 09:30:49 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:44:52 UTC