1777903 - Add tentative WPT for checking the handling of `insertParagraph` and `insertLineBreak` in inline editing host

Status: RESOLVED FIXED

(Core :: DOM: Editor, enhancement, P2)

Description

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

We sometimes get bug reports about <span contenteditable>, and the insertParagraph and insertLineBreak command handling of Chrome is a little bit odd. Chrome may insert <div> element into <span>. So, if <span contenteditable> becomes widely used, we might need to follow the odd behavior, but I'd like to avoid such future...

Comment 1

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

Attachment: Bug 1777903 - Add tentative WPT of handling line breaks in inline editing host r=m_kato

Browsers shouldn't insert <div> and <p> elements into inline elements such
as <span> even when it's display value creates a block format context since
it's invalid structure from point of view of HTML. However, some browsers do
it. Therefore, this test should make them fail.

The reason why this patch touches editor-test-utils.js is, it scans the
following <script> element's text with a bug. So the change makes it does
not scan outside the editing host.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/e3fd1571e2b9
Add tentative WPT of handling line breaks in inline editing host r=m_kato

Comment 3

[Cristian Tuns]

https://hg.mozilla.org/mozilla-central/rev/e3fd1571e2b9

Comment 4

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/34781 for changes under testing/web-platform/tests

Comment 5

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Upstream PR merged by moz-wptsync-bot