Re: [w3c/editing] Standardize execCommand("insertParagraph") in inline editing host (#175)

> but I would prefer not to spend more time on execCommand, as we are really trying to move away from it,

Is there another API to modify DOM tree like execCommand?

> and we have seen that editors have stopped using it about a decade ago.

Even if spec editors have already given up standardize with a spec, Mozilla cannot stop working on it since there are a lot of incompatibility especially with Blink/WebKit and that make Firefox users inconvenient on some web apps. So, when we change Firefox's behavior, we want to include new tests into wpt. But in my understanding, a browser vendor shouldn't do it without filing issues.  Therefore, I keep filing this kind of issues when I need to fix incompatibility issues of undocumented editor behavior.

> It would be much more helpful if you for example could implement the beforeinput event.

FYI: I'm working on `InputEvent.inputType` and after that, I'll work on implementing `beforeinput`. But unfortunately, `InputEvent.inputType` requires me to understand Gecko's editor really deeper and I'm working on refining Gecko's editor design for making possible to implement them. (And I'm still thinking we should implement which `beforeinput` event (Blink's vs. WebKit's) on Firefox since they are really different...)

-- 
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/175#issuecomment-386979269