IME composition
spec
cited
open
compositionend vs input event order differs across browsers (isComposing guard)
Event order between compositionend and input is inconsistent across browsers
w3c/uievents · w3c/uievents
Symptom
The spec orders input before compositionend (Chrome and Safari follow it), but Firefox and Edge fire input after compositionend, so isComposing-based guards behave differently per browser.
Minimal repro
Log the input and compositionend events while committing a CJK composition in Chrome versus Firefox; their relative order differs.
Fix
Define a canonical order in the spec; frameworks should not assume input fires before compositionend.