W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2008

[whatwg] Should enter be mapped to click?

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 16 Dec 2008 23:44:12 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0812162344050.30225@hixie.dreamhostps.com>
On Tue, 15 Jul 2008, Anne van Kesteren wrote:
> On Tue, 15 Jul 2008 09:50:25 +0200, Ian Hickson <ian at hixie.ch> wrote:
> > On Mon, 14 Jul 2008, Aaron Leventhal wrote:
> > > 
> > > Now that tabindex can be used on any element to make it focusable, it
> > > makes sense that it should be possible to trigger a click on those
> > > elements with the keyboard.
> > > 
> > > Opera maps Enter to click. As far as I know, other browsers only do that
> > > for a few elements like<a>.
> > > 
> > > What do people think? Should it be spec'd?
> > 
> > 3.4.1.7. Interactive content, paragraph 3:
> > 
> > | When activation is performed via some method other than clicking the
> > | pointing device, the default action of the event that triggers the
> > | activation must, instead of being activating the element directly, be to
> > | fire a click event on the same element.
> 
> Last I checked that doesn't say each focusable element actually gets
> activation behavior as well. Here's an example:
> 
>   <div tabindex=0 onclick=alert(0)>TEST</div>
> 
> The specification states that only certain elements are "interactive 
> content", not everything that's focusable.

Fixed.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 16 December 2008 15:44:12 UTC

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