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

[whatwg] Should enter be mapped to click?

From: Anne van Kesteren <annevk@opera.com>
Date: Mon, 14 Jul 2008 14:29:31 +0200
Message-ID: <op.ud97necu64w2qv@annevk-t60.oslo.opera.com>
On Mon, 14 Jul 2008 11:03:23 +0200, Aaron Leventhal <aaronlev at moonset.net>  
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?

Yes :angel:

Seriously though, I think it makes sense that focusable elements have  
activation behavior and that you can trigger that by both the keyboard and  
mouse.


> At least the spec should say what elements map enter to click now.  
> Except for perhaps<textarea>  and a few form controls, I don't see why  
> some should and others not, though. Maybe it should be a blacklist?

I'm not sure it should go further then suggesting "Enter" to be the key  
for performing form submission, etc. After all, there's a lot of clients  
out there without an "Enter" key.


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Monday, 14 July 2008 05:29:31 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:03 UTC