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

I came across this as a problem for my own use case where I discovered that Safari/Chrome were triggering `compositionend` before `keydown` including for the ENTER keypress which concluded composition - resulting in a `KeyboardEvent` where the code is "Enter" and `isComposing` is `false` - but that enter keypress was - in fact - used to conclude a composition. 

I don't have the level of expertise to contribute towards a solution here, but it seems that there was some productive conversation in this thread which dried out and didn't end up leading anywhere. Is this viewed as a non-issue? What should developers be doing to avoid triggering incorrect events on keyboard events which are actually due to international character composition?

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