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

扂�玴肪漈麜藉樨ж鉞救埱輓纂ˉ棨骳遘齥恘歇匯糊eydown/up/press紱釬﹝怀�賰侈樼笰埱遣芠椕壧恘殿襤智�岆謗鎢岈﹝垀眕婓怀�賰侈樼窐探扑▎eydown/up/press岆竭察祑腔岈①﹝

蕉藉mobile炵苀憩載ь奠賸ㄛ婓mobile炵苀爵ㄛ怀�賰釆蛹齙芚�肮衾modal dialogㄛ垀衄瑩攫紱釬茼蜆岆掩俇�娃蚢傿纂�

峔珨扂蠅褫眕諉忳腔岆坳楷堤珨郪杻隅腔瑩硉ㄛ瞰�蝜��扔贏萺�岆keydown 229樓奻keyup妗暱偌瑩﹝


む妗載樓歲�佽騫マalue change腔恀枙﹝獗森泂ㄩ
http://www.cnblogs.com/cathsfz/archive/2011/05/29/2062382.html#2145980

眈掀楷堤keypress岈璃ㄗ妗暱奻珋婓羶�劼熁棚鬕岡爰�祥夔諉忳腔岆楷堤input/textinput/change岈璃﹝


2011/8/12 Kang-Hao (Kenny) Lu <kennyluck@w3.org>

> **
> �� Web App 馱釬瞎滖�穔鹹籟炭鯜獃мf���賰侃睍M趼腔�r緊祥�肴�茦追潬屜岈璃ㄗkeydown﹜keyup 摯
> keypressㄘ腔珨虳��扴ㄛ扂�]衄豝��秏趙ㄛ祥綎壺賸 2. 腔����艘れ�簅僊��肴�岆�朴纂�
>
> 憩呾�]衄毀�考瑲�扂��珩褫眕眻諉挲☆盓厥★ㄛ湮模崋�N砑ˋ
>
> 埻恅腔�黕禜髦跋1]ㄛ婓�@��赩璃蹈桶奻眈燊腔������衄ㄩ
> * 蚚���賰迄藦��r input.value 掩載蜊腔①倛[2]
> * Google Japan 腔���賰� API[3] 〞 孬醱恅�n燊黺 IME 腔賡畿衄�Dㄛ��耷硉腕艘腔
>
> [1] http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/0749
> [2] http://lists.w3.org/Archives/Public/public-html-ig-zh/2011Feb/0030
> [3] http://lists.w3.org/Archives/Public/public-html-ig-zh/2011Feb/0021
>
>
> Kenny
>
>
>
> -------- Original Message --------  Subject: Re: ISSUE-137 (IME-keypress):
> Should keypress events fire when using an IME? [DOM3 Events]  Resent-Date:
> Tue, 09 Aug 2011 08:58:20 +0000  Resent-From: public-webapps@w3.org  Date:
> Tue, 09 Aug 2011 17:57:22 +0900  From: Masayuki Nakano
> <masayuki@d-toybox.com> <masayuki@d-toybox.com>  To: Web Applications
> Working Group WG <public-webapps@w3.org> <public-webapps@w3.org>
>
> Hello.
>
> Currently, Firefox doesn't fire any key events (keydown, keyup and
> keypress) during IME composition.  There are some reasons:
>
> 1. Most firefox code handles key events without IME composition state
> check. (This is our internal reason, though) Therefore, if we would fire
> key events during composition, we would need to fix very many code.
>
> 2. Web application developers cannot check IME composition state
> directly.  If they needed to check it, they needed to listen
> compositionstart and compositionend events and make a bool variable.
> Therefore, if web developers handled key events without IME state check,
> IME users couldn't use some web applications.
>
> 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.
>
> 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> <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.
> > ]]
>
> --
> Masayuki Nakano <masayuki@d-toybox.com> <masayuki@d-toybox.com>
> Manager, Internationalization, Mozilla Japan.
>
>
>