18931 2012-09-20 09:17:36 +0000 D3E should define when compositionupdate event is fired 2013-08-26 16:29:01 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - DOM3 Events unspecified All All RESOLVED FIXED P2 normal --- 1 masayuki travil garykac kochi mike www-dom public-webapps-bugzilla oldest_to_newest 74124 0 masayuki 2012-09-20 09:17:36 +0000 I forgot to file this issue here. I mentioned this in the ML but nobody never replied this: http://lists.w3.org/Archives/Public/www-dom/2012JanMar/0239.html > I think D3E spec should define the timing of compositionupdate event clearly. > > On IE9, compositionupdate event is fired *after* editor content is modified actually. > > On WebKit and Gecko, it's fired *before* editor content is modified. > > That means there is a difference. That is, whether web app can access modified content by value of <input> or <textarea>, or innerHTML of editing host of a contenteditable element. > > I think that most web application developers expect IE9's behavior because compositionupdate isn't cancelable and they may want to access the modified value. > > For the compatibility between browsers, I'd like to suggest that D3E should define the timing. I recommend the IE9's behavior. 91184 1 kochi 2013-07-24 00:26:58 +0000 Here are relevant bugs filed for WebKit and Chromium: (though they are talking about 'compositionend' event) https://bugs.webkit.org/show_bug.cgi?id=31902 https://code.google.com/p/chromium/issues/detail?id=41945 91185 2 travil 2013-07-24 00:37:03 +0000 Proposed spec text (replaces existing paragraph after the event definition): A user agent SHOULD dispatch this event during a composition session when a text composition system updates its active text passage with a new character, which is reflected in the string in CompositionEvent.data. In text composition systems which keep the ongoing composition in sync with the input control, the compositionupdate event SHOULD be dispatched after the control is updated. Some text composition systems might not expose this information to the DOM, in which case this event will not fire during the composition process. If the composition session is canceled, this event will be fired immediately before the compositionend event, and the CompositionEvent.data attribute will be set to the empty string. 91212 3 masayuki 2013-07-24 07:14:43 +0000 If we will define "input" event, we need to define the order with "input" event too (not so important, though). 91272 4 kochi 2013-07-25 09:24:34 +0000 Also for compositionend event? ORIGINAL ============== A user agent must dispatch this event when a text composition system completes or cancels the current composition session. This event is dispatched immediately after the text composition system completes the composition session (e.g., the IME is closed, minimized, switched out of focus, or otherwise dismissed, and the focus switched back to the user agent). ============== NEW ============== A user agent must dispatch this event when a text composition system completes or cancels the current composition session, and the compositionend event SHOULD be dispatched after the control is updated. This event is dispatched immediately after the text composition system completes the composition session (e.g., the IME is closed, minimized, switched out of focus, or otherwise dismissed, and the focus switched back to the user agent). ==============