[Bug 23909] Which is expected whether keydown event is fired before or after native IME handles it

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23909

--- Comment #2 from Masayuki Nakano <masayuki@d-toybox.com> ---
(In reply to Travis Leithead [MSFT] from comment #1)
> Overall, I think this is an implementation detail, and not one that the W3C
> spec can specify across different IMEs/platforms.

This may make difference of some attributes of KeyboardEvent.

If the case of bug 23910 should set IME inputting character to the .key value,
keydown event must be handled after native IME handles it.

Additionally, e.g., on Linux, there is no way to cancel composition even if
keydown event is consumed by web apps by a call of preventDefault(). If browser
dispatches keydown event before IME handles the event, browser can prevent
starting composition with consumed keydown event. However, if we do so,
keydowen event's .key value must be input text without IME.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 10 December 2013 08:36:31 UTC