Closed
Bug 1921171
Opened 2 years ago
Closed 1 year ago
Add WPT for the cases which `contenteditable=true` and `contenteditable=plaintext-only` are nested
Categories
(Core :: DOM: Editor, enhancement)
Core
DOM: Editor
Tracking
()
RESOLVED
FIXED
137 Branch
| Tracking | Status | |
|---|---|---|
| firefox137 | --- | fixed |
People
(Reporter: masayuki, Assigned: masayuki)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
See https://github.com/w3c/editing/issues/470. This bug may be invalid.
|
Assignee | |
Comment 1•2 years ago
|
||
Probably, we need only to add automated tests because it seems that all vendors agreed that outermost editing host's contenteditable value should be applied anywhere.
Assignee: nobody → masayuki
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Summary: Implement the behavior when `contenteditable=true` and `contenteditable=plaintext-only` are nested → Add WPT for the cases which `contenteditable=true` and `contenteditable=plaintext-only` are nested
|
|
Assignee | |
Comment 2•1 year ago
|
||
Adding the tests for the conclusion of https://github.com/w3c/editing/issues/470.
If contenteditable="true" (="") and contenteditable="plaintext-only"
without contenteditable="false", the outermost editing host should consider
whether it's a richtext editor or a plaintext editor.
Pushed by masayuki@d-toybox.com:
https://hg.mozilla.org/integration/autoland/rev/ecc241ac8ebc
Add WPTs to check the editing behavior when `contenteditable="plaintext-only"` and `contenteditable="true"` are nested r=smaug
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/51035 for changes under testing/web-platform/tests
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox137:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 137 Branch
Upstream PR merged by moz-wptsync-bot
You need to log in
before you can comment on or make changes to this bug.
Description
•