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

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

Thanks, that's what I want to know.

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

Sigh... Although it's off topic, implementing Level 1 is looks reasonable for us since Safari's implementation looks odd in some cases. On the other hand, Level 1 cannot cancel inputs from keyboard, so, it cannot replace legacy keypress event...

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