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

I've begun working on a formal algorithm for these events and have the current draft in:

https://docs.google.com/document/d/1LJQvjEmWZGzVgZnofpvdkxMj1hEnLniD72XD4DLJWx4/edit?usp=sharing

I've used the `compositionupdate` -> `beforeinput` -> `input` ordering, and added a reference to this issue.

-- 
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-668276305