Re: [w3c/uievents] Event order between "compositionend" and "input" (#202)

Currently, DOM composition events do not support of committing a part of composition. In such case, Firefox commits existing composition first, then, restart composition with new range.

Brian, you can check this behavior even with MS-IME.
1. Open preferences dialog
2. Press key assign from "Microsoft IME" to "ATOK"
3. Type something which may cause 2 or more clauses.
4. Type Space bar to convert.
5. Type ArrowDown key.

And also, new line key handling is not defined under UI Events unfortunately. In most cases, Enter key press during composition of Japanese IME just commits composition. However, for example, Enter key press during composition of Korean IME causes both committing composition and inserting a new line. If all browsers support beforeinput, the new line input can be represented with it which should be fired immediately after compositionend.  However, now, Firefox dispatches a set of key events (i.e., keydown, keypress and keyup events) after compositionend on Windows, and dispatches only keypress event after compositionend on macOS. So, this issue should be out of scope of this.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/issues/202#issuecomment-409838063