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

> Is there another API to modify DOM tree like execCommand?

I am not sure what you mean. What is being used by editors as of today is the standard API to change the DOM tree -- things like `insertAdjacentHTML`, `setAttribute`, `getAttribute`, `replaceChild`, etc. . Execcommand is still used in a few places where there is no alternative.

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

Ok, if it's important to Mozilla, I understand. Just be aware that JS editors have moved away from using it in most cases (save above-mentioned exceptions). Just making sure you are aware that it's not how JS editors manipulate the DOM in most cases.

> 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...)

Understood and thanks for that info. The level 2 of the implementation (what Webkit has) is what has been arrived at through the discussions about requirements on the part of JS editors. Level 1 is something Chrome decided to do because they could for various reasons not ship level 2. Level 1 can work as an additional aid for making an editor, but one really has to continue to work with the APIs already used now for most things. Webkit's implementation is both level 1 and level 2 compliant. I hope Chrome can eventually get to level 2 or we can agree on a new level 3 that everyone can agree on.


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