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

We've already discussed about this.

At that time, compositionupdate should be cancellable and if it's cancelled, DOM shouldn't be modified for JS-IME. However, now, compositionupdate isn't cancellable. So, this reason does not make sense.

However, I think that there is input event which is implemented by all browsers and handling it allows web developers to handle any input. Therefore, firing compositionupdate before modifying DOM is better at least for now (beforeinput hasn't been implemented yet).

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/issues/66#issuecomment-173043732