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

During the F2F, we agreed on the following order:

beforeinput
compositionupdate
<update DOM now>
input

Current browser behavior is:
 IE/Edge fire compositionupdate after the DOM has been modified
 Moz/Saf/Chrome fire it before the DOM has been modified.
So this requires that Edge updates its behavior so that all the browsers can have the same behavior/

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