Re: ISSUE-137 (IME-keypress): Should keypress events fire when using an IME? [DOM3 Events]

(11/08/09 16:57), Masayuki Nakano wrote:
> 3. Some web developers may not know well about IME behavior. Their web
> applications might break IME behavior by handling key events.
>
> I'd like to *suggest* that key events shouldn't be fired during IME
> composition, especially for #3.  If web developers want to know the
> timing of updating composition string, they can use compositionupdate
> or textinput. I think that these events are better for the purpose
> since IME composition string can be updated by clicking on candidate
> window, i.e., it doesn't cause key events.

A few Chinese web developers support Nakano-san's opinion here. In
addition, we are concerned about the situation with other events such as
input, textinput and change. We think these event *shouldn't* be fired
during IME composition, and we are not sure if that's already specced
somewhere.


Kenny

>
> thanks,
>
> On 2010/10/06 15:16, Web Applications Working Group Issue Tracker wrote:
>>
>> ISSUE-137 (IME-keypress): Should keypress events fire when using an
>> IME? [DOM3 Events]
>>
>> http://www.w3.org/2008/webapps/track/issues/137
>>
>> Raised by: Doug Schepers
>> On product: DOM3 Events
>>
>> Hallvord R. M.
>> Steen<http://lists.w3.org/Archives/Public/www-dom/2010JulSep/0176.html>:
>> [[
>> current spec text says about the keypress event:
>>
>>> This event type shall be generated after the keyboard mapping
>>> but before the processing of an input method editor, normally
>>> associated with the dispatching of a compositionstart,
>>> compositionupdate,
>>> or compositionend event.
>>
>> I think this is wrong, if an IME is actively processing the input no
>> keypress event should fire.
>> ]]
>

Received on Tuesday, 16 August 2011 22:56:48 UTC