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

@masayuki-nakano  specing this makes sense. I think, @johanneswilm is the formal spec editor for ExecCommand spec so I would say this GitHub issue tracker as close as it gets to it. :)

I would also propose making a change in the spec to explicitly state assumption for caret position at the time of running insertParagraph command (we are currently assuming that the caret is at the end of string). 

When the caret position is not at the end of the string, expected behavior could be different.

I found few other issues in Chrome using your test cases (I think they are bugs but Blink folks should probably weigh in on this) which have same broken behavior as Gecko.
This is what I tested on Windows 10 recent insider's build for Chrome:
[https://jsfiddle.net/d_toybox/x0kohuo0/9/ (|<a name="foo">|)](https://jsfiddle.net/d_toybox/x0kohuo0/9/ (|<a name="foo">|)) possibly a bug on Chrome
[https://jsfiddle.net/d_toybox/x0kohuo0/10/ (|<a href="foo">|) ](https://jsfiddle.net/d_toybox/x0kohuo0/10/ (|<a href="foo">|) ) possibly a bug on Chrome
nested case:
[https://jsfiddle.net/d_toybox/x0kohuo0/13/ (|<b><a href="foo">|)](https://jsfiddle.net/d_toybox/x0kohuo0/13/ (|<b><a href="foo">|)) possibly a bug on Chrome





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