- From: Masayuki Nakano <notifications@github.com>
- Date: Tue, 04 Jul 2023 22:07:49 -0700
- To: w3c/uievents <uievents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 5 July 2023 05:07:56 UTC
About vs. `beforeinput`, I think that the better event (i.e., `beforeinput`) should be fired because if the default of `beforeinput` is prevented, `textInput` should not be fired and that behavior makes sense for modern editor apps since they can save the dispatching cost of `textInput`. About 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`. Therefore, I think that `compositionupdate` -> `beforeinput` -> `textInput` -> `input` is reasonable. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/uievents/issues/353#issuecomment-1621032371 You are receiving this because you are subscribed to this thread. Message ID: <w3c/uievents/issues/353/1621032371@github.com>
Received on Wednesday, 5 July 2023 05:07:56 UTC