Closed Bug 1921928 Opened 25 days ago Closed 17 days ago

Add automated tests of `delete` and `forwardDelete` in `contenteditable=plaintext-only`

Categories

(Core :: DOM: Editor, task)

task

Tracking

()

RESOLVED FIXED
133 Branch
Tracking Status
firefox133 --- fixed

People

(Reporter: masayuki, Assigned: masayuki)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

It seems that Chrome and Safari handle deletion in contenteditable=plaintext-only as same as in contenteditable=true. So, perhaps, we don't need to change our delete handlers, but at least we need to add WPTs for basic cases to check whether it's true.

contenteditable=plaintext-only can have any complicated DOM tree. And there
is no reason to make contenteditable=plaintext-only behave differently from
contenteditable=true when making block empty or joining block boundaries.
Therefore, the tests compares the behavior in the same browser rather than
between browsers. The compatibility between browsers should be tested with
contenteditable=true in the other tests.

Depends on D224188

Pushed by masayuki@d-toybox.com: https://hg.mozilla.org/integration/autoland/rev/766b2003cf82 part 1: Add automated tests to check whether deletion around line breakers and block boundaries r=m_kato https://hg.mozilla.org/integration/autoland/rev/9c85d8b4f15c part 2: Add tests to check `delete`/`forwardDelete` around consecutive white-spaces when they are preserved r=m_kato
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/48527 for changes under testing/web-platform/tests
Status: ASSIGNED → RESOLVED
Closed: 17 days ago
Resolution: --- → FIXED
Target Milestone: --- → 133 Branch
Upstream PR merged by moz-wptsync-bot
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: