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

> - Making the spec's description more complex: "`isComposing` is set when composing, EXCEPT when..." (ugh)

How about: "`isComposing` is true when the text is still composing by composition" or something similar? I'm trying to say, when `isComposing` is true, its data may be updated/replaced during current composition. So, the data hasn't been fixed yet.

> - Making things slightly harder for devs who need to ignore `input` events during composition (since they have to add an event handler for `compositionend`).

I have no idea what the use-case of ignoring all input caused by composition. I suggested current `isComposing` but I intended to make `input` event useful for suggesting use-case because I didn't realize the event order difference between browsers (`input` vs. `compositionend`).

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