[w3c/uievents] `beforeinput` and `compositionupdate` event order (Issue #354)

> About [`beforeinput`] vs. `compositionupdate`, I'm surprised at the event order in Chrome. `compositionupdate` represents the composition string change, it does not depend on editing content from UI Events spec point of view. Therefore, I think that the builtin editor should handle `compositionupdate` and dispatch `beforeinput` and `input` (as its default action). Therefore, I think that `compositionupdate` -> `beforeinput` -> `textInput` -> `input` is reasonable.

_Originally posted by @masayuki-nakano in https://github.com/w3c/uievents/issues/353#issuecomment-1621032371_

The event order of typing `´a` in an input field in Chrome is (see https://github.com/w3c/uievents/issues/353#issuecomment-1620349355):

- keydown
- compositionstart
- beforeinput
- compositionupdate
- input
- keyup
- keydown
- beforeinput
- compositionupdate
- textInput
- input
- compositionend
- keyup

cc @chrishtr

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/issues/354
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/uievents/issues/354@github.com>