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

> because there can be (and are) inline formatting things that the browser doesn't really understand as easily as `<a>`. For example, what should the browser do if the user hits enter in this case:
> ```
>  <p>Hello <span class="actor-name">Peter[]</span></p>

Well, I don't think that this case should be cared by browsers since contenteditable/designMode do not have built-in UI to modify semantics of each element and such case really depends on what web apps intent. So, if web apps need to provide such additional meaning with `<span>` or something, they should manage by themselves. (So, I believe that contenteditable/designMode are just rich text editor rather than HTML editor.)

> Additionally, paragraph splitting is best left to JavaScript, because there are 1000s of ways that paragraph splitting and merging could be done, and without domain knowledge of the text's contents, you're really making a blind guess as to what is right.

Yeah, but Mozilla needs to keep compatibility with Blink and WebKit as far as possible due to market share difference. So, if we (Mozilla) want to add wpt for such undocumented behavior, we'd like to know what other browser vendors think.  If at least another vendor agree with proposed behavior and that becomes common behavior of some browsers, I believe that that can be included into wpt.

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