Re: [w3c/uievents] Should DOM be modified before or after compositionupdate? edge/IE do one thing, chrome/saf/firefox do another? (#66)

I know there was a resolution, but can we swap `'compositionupdate'` and `'beforeinput'` so the event order becomes:
```
*'compositionupdate'
*'beforeinput'`
-update DOM now-
'input'`
```
**Reasoning**
1. Previously we want to fire `'beforeinput'` before `'compositionupdate'` because IE/Edge has a different behavior, but IIRC @gked mentioned that it was a bug and will be fixed. (@gked can you help confirm?)
2. If IE/Edge could update the behavior then it makes more sense to fire `'beforeinput'` immediately before DOM update as required by spec:
    > A user agent MUST dispatch this event when the DOM is about to be updated.
3. We want to fire `'beforeinput'/'input'` for `'deleteCompositionText'` and `'insertFromComposition'` at the end of composition without `'compositionupdate'` (since it's not a request from IME), so it doesn't make sense to constrain `'compositionupdate'` in between `'beforeinput'/'input'`.

-- 
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/66#issuecomment-268070654