W3C home > Mailing lists > Public > www-dom@w3.org > April to June 2011

Re: ISSUE-142 (multiple keypress): one keydown might fire multiple keypress/textInput events [DOM3 Events]

From: Doug Schepers <schepers@w3.org>
Date: Wed, 11 May 2011 16:30:34 -0400
Message-ID: <4DCAF1EA.7070503@w3.org>
To: "www-dom@w3.org" <www-dom@w3.org>
CC: "Hallvord R. M. Steen" <hallvord@opera.com>
Hi, Hallvord-

I've now added wording regarding keys associated with multiple characters.


I tried to account for the fact that multiple keypress events might be 
fired, but for cases where the default is only a textinput event, it 
should conflate the characters into a single event (as with a paste 

Please let us know if this satisfies your issue.


Web Applications Working Group Issue Tracker wrote (on 10/6/10 2:24 AM):
> ISSUE-142 (multiple keypress): one keydown might fire multiple keypress/textInput events [DOM3 Events]
> http://www.w3.org/2008/webapps/track/issues/142
> Raised by: Doug Schepers
> On product: DOM3 Events
> Hallvord R. M. Steen<http://lists.w3.org/Archives/Public/www-dom/2010JulSep/0181.html>:
> [[
> Spec text on keydown event
> http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#event-type-keydown
>>  if the key is associated with a character, the default action
>>  shall be to dispatch a textInput event with the character as
>>  the value of the TextEvent.data attribute
> uses singular forms ('a textInput event') which doesn't take into account
> that a single keydown event might cause several keypress (->  textInput)
> events.
> Trivial example: press a dead key twice. The default action of the second
> keydown will be to fire two keypress and two text input events.
> More far-fetched: use a keyboard layout where some keys are mapped to
> input several characters. Chrome, Firefox and IE (on Windows) agree on
> firing keydown, multiple keypress (and multiple textInput if supported),
> single keyup.
> Suggested text:
> <li>if the key inserts one or more characters, the default action shall be
> to dispatch one<a class="eventtype"
> href="#event-type-textInput"><code>textInput</code></a>  event for each
> character inserted, with that character as the value of the<a
> href="#events-TextEvent-data"><code>TextEvent.data</code></a>  attribute
> (Leaving aside for a moment the issue that I would also like to replace
> textInput with keypress in that text..)
> ]]
Received on Wednesday, 11 May 2011 20:30:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:17 UTC