Closed Bug 1675779 Opened 5 months ago Closed 2 months ago

HandleDeleteAtomicContent should handle non-editable text node

Categories

(Core :: DOM: Editor, defect, P3)

Unspecified
All
defect

Tracking

()

RESOLVED FIXED
88 Branch
Tracking Status
firefox88 --- fixed

People

(Reporter: m_kato, Assigned: m_kato)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

No description provided.

Since WSScanResult can return non-editable text node,
HandleDeleteAtomicContent is called with non editable text node, then it is
failure.

So if non editable text node is returned by WSScanResult, we use parent
content of this text node instead.

browserscope is no longer maintained, so contenteditable=false case is
incorrect now. So I would like to update this tests for non editable case.

Depends on D96298

Attachment #9186432 - Attachment description: Bug 1675779 - HandleDeleteAtomicContent should handle non-editable text node. → Bug 1675779 - HandleDeleteAtomicContent should handle non-editable text node. r=masayuki
Attachment #9186433 - Attachment description: Bug 1675779 - Update browserscope for contenteditable=false case. → Bug 1675779 - Update browserscope for contenteditable=false case. r=masayuki
Pushed by m_kato@ga2.so-net.ne.jp:
https://hg.mozilla.org/integration/autoland/rev/edd38c6dc831
HandleDeleteAtomicContent should handle non-editable text node. r=masayuki
https://hg.mozilla.org/integration/autoland/rev/1ad746378bd9
Update browserscope for contenteditable=false case. r=masayuki
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/27724 for changes under testing/web-platform/tests
Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 88 Branch
Upstream PR merged by moz-wptsync-bot
You need to log in before you can comment on or make changes to this bug.