Re: [w3c/editing] insertParagraph definition is different from current browsers' behavior when selection is collapsed at end of inline element(s) (#172)

> Ok, but is there any editor in the world that does not use at least one custom element?

Personally, I don't worry about such web apps since such web apps need to manage such custom elements by themselves anyway. Most compatibility issues reported to us are, web developers only tested with Chrome (and perhaps Safari) even though they wrote a code depending on non-standardized behavior. I.e., such web apps are handling input or using existing editing API roughly.

> But I'm a little afraid we can get distracted by trying to standardize paragraph merging and splitting (which quickly can turn into a very long debate) as well as standardizing execCommands commands that are no longer used.

Even if web apps don't use insertParagraph command directly, if they don't override Enter key press, the command is executed indirectly. So, execCommand is used forever indirectly.

-- 
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/172#issuecomment-388730801

Received on Monday, 14 May 2018 08:03:59 UTC