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

That's a fair point. I hadn't thought about multi-line input so much.

So with the proposal to make `isComposing` false for the last `input` event before the (last?) `compositionend` the author:
* will no longer need to track `compositionstart` / `compositionend` in order to ignore inputs while composing, but
* _will_ need to track `compositionstart` / `compositionend` in order to differentiate between an input that commits part of the composition, and an input that is not part of composition.

Does that sound right?

(I'm actually a bit confused now about if this proposal works in light of multiple `compositionend` events. The IMEs I use on Linux and Windows don't allow committing part of a composition string so I never get more than one `compositionend` event.)

-- 
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-407601959