Re: [w3c/editing] Should execCommand dispatch beforeinput or not? (#200)

> It's impossible to use it for what you mention as long as the editor supports at least one operation that requires JavaScript dom manipulation. Even if you create an editor that only does those things that are covered by execCommand, it will not work because only using browser built-in operations means that it will produce different HTML in different browsers.

Is it true for some simple commands like `insertText`, `insertLineBreak`, `insertParagraph` and `delete` with simple DOM tree? (If so, I'd like to fix such incompatibility issues as far as possible after finishing implementing`beforeinput` event on Firefox.)

> If there is no interest from the JavaScript side in `execCommand` - why are we (again) wasting all this time on it?

I don't think "waste" is good term for `execCommand`. Both backward and cross browser compatibility of (unfortunately) existing API are important if they can be fixed by browser side.

-- 
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/200#issuecomment-528190681