Add automated tests of `delete` and `forwardDelete` in `contenteditable=plaintext-only`
Categories
(Core :: DOM: Editor, task)
Tracking
()
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.
Assignee | ||
Comment 1•22 days ago
|
||
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
Assignee | ||
Comment 2•22 days ago
|
||
Depends on D224577
Comment 5•17 days ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/766b2003cf82
https://hg.mozilla.org/mozilla-central/rev/9c85d8b4f15c
Description
•