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

@ojanvafai @dtapuska

So the conclusion is we don't fire `beforeinput/input` for `execCommand()`, but how do we handle backward compatibility?

*e.g.* Currently `execCommand()` fires `input` in **WebKit** and **Gecko** (actually **Edge** as well), are we sure that it won't break the Web if we changed the behavior?

Suggestion: Can we dispatch `non-cancelable` `beforeinput/input` for `execCommand()` if the main concern is safety?

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

Received on Monday, 20 June 2016 19:37:44 UTC