Re: DOM3 Key events

Wow, that was quite a long time ago, it still doesn't negate the need  
for the event to be defined.

All the major browsers, and most ui toolkits i am aware of follow the  
keydown->keypress->keyup style model, whereas some of the post in  
that thread seemed to think keypress should come after keyup, which  
seems downright bizarre.

WebKit always sends a keyDown, even for repeat characters (as windows  
does not appear to distinguish between multiple keydowns, and holding  
a keydown) this means that there's always an event that can be hooked  
into, even during IM composition when we don't send keypress/ 
textinput (lest we break sites :-/)

--Oliver

On 1/08/2007, at 3:07 PM, L. David Baron wrote:

> On Wednesday 2007-08-01 14:42 -0700, Oliver Hunt wrote:
>>   * The behaviour and interaction (and existence) of a keypress
>> event is completely absent.  While the keypress events are (to a
>> greater or lesser extent) evil, they are used extensively on many
>> websites, and are supported by all major browsers, so not defining
>> behaviour will leave us trapped in the awful quagmire of
>> incompatibility that already exists.
>
> keypress events are also critical for capturing system key repeating
> behavior (rather than have the Web author try to guess how the system
> does key repeating).  This is particularly important for events that
> don't generate text (e.g., arrow keys, backspace).
>
> See http://lists.w3.org/Archives/Public/www-dom/2005JanMar/0002 for
> slightly more detail (the previous time I raised this issue).
>
> -David
>
> -- 
> L. David Baron                                 http://dbaron.org/
> Mozilla Corporation                       http://www.mozilla.com/