<80545739-CCBC-411C-B247-349E9C722831@apple.com>
Current votes: None.
On Sep 20, 2007, at 4:33 AM, Asbj=F8rn Ulsberg wrote: > On Thu, 20 Sep 2007 13:03:03 +0200, Maciej Stachowiak =20 > <mjs@apple.com> wrote: > > First I have to say that I really like the suggestion. What's =20 > missing, though, is a way to bind a command to an actual action in =20 > the document. Is this done via a "command" attribute, via scripting, =20= > or both? With the "onclick" attribute or programmatic "click" or "DOMActivate" =20= event listeners. Note that these events bubble, so this could =20 automatically activate another element by nesting. The not-yet-defined =20= command attribute may allow you to active an arbitrary other element. =20= It may also be useful to add a "focus" command type to automatically =20 focus another element, if this is expected to be a commonly desired =20 keyboard shortcut so that it should be doable without script. (With =20 script you can just call focus() on the element to be focused from the =20= command's onclick handler). I can imagine wanting a shortcut to focus =20= a page's search field for instance. If shortcutkey=3D"" is allowed on other types of command-defining =20 elements, you could make a link command using an <a> element. >> <command label=3D"Compose New Message" shortcutkey=3D"n 1"> > > Could perhaps "shortcutkey" be shortened to just "key" or =20 > "keys" (since multiple keys can be bound to one command)? The idea is that only one key binding is created, but the client may =20 give multiple prioritized suggestions. It has been pointed out that =20 XHTML2 adds an <access> element with a key=3D"" attribute, so perhaps =20= key would be a good choice. Regards, Maciej