Re: [w3c/uievents] preventDefault() of keydown event should not kill composition start caused by the keydown (#180)

Please note that, native IME may handle native key down event **before** browser receives it. When you see `keyCode === 0xE5` of `keydown` event before `compositionstart`, it means that the `keydown` event has **already** been handled by IME (at least on Windows). That's the reason why current spec does not make sense technically.

-- 
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/180#issuecomment-551863467