Re: [w3c/editing] beforeinput should be fired only when the DOM change is caused by direct input by keypress or composition (#43)

> as long as we are OK with the non-paired events and the different firing conditions between beforeinput&input

Given that execCommand doesn't follow any spec, and it's just something we don't touch much because it is used in existing code, I think it is ok for it to behave out of somewhat out of order. At least that is much better than us adding beforeedit events that a lot of JS code will need to learn to disregard.

---
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/editing/issues/43#issuecomment-227268472