[meta] Bug 685445 has regressed (Contenteditable=false elements in contenteditable=true elements cannot be deleted by using Backspace/Delete)
Categories
(Core :: DOM: Editor, task)
Tracking
()
People
(Reporter: emilio, Assigned: m_kato)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Keywords: meta)
Attachments
(4 obsolete files)
+++ This bug was initially created as a clone of Bug #685445 +++
I can reproduce the issue using the test-case in the bug.
Makoto, it seems you fixed bug 1394758, is there any chance you could take a look?
| Reporter | ||
Updated•5 years ago
|
additional test case/simple codepen, https://codepen.io/burritoiand/pen/xxVJdaL, try deleting the text in FireFox, thanks!
Comment 3•5 years ago
|
||
Hi, I tried to get a regression range for this issue by using the steps from Comment 2 but it seems to be happening all the way down to Fx 43. I will remove the regression window flag.
Updated•5 years ago
|
| Assignee | ||
Updated•5 years ago
|
| Assignee | ||
Comment 6•5 years ago
|
||
| Assignee | ||
Comment 7•5 years ago
|
||
Even if non-editable node, DeleteNodeWithTransaction should be able to
remove it if parent is editable.
Example, <div contenteditable><img contenteditable=false /></div> should
allow to remove <img> element by backspace key.
| Assignee | ||
Comment 8•5 years ago
|
||
Depends on D92582
| Assignee | ||
Comment 9•5 years ago
|
||
Actually, we handle non-editable node as special node like <img>.
WSRunObject scans text node for white space handling, and reason content is
sometimes leaf node (text node). But since we use reason content for
HandleDeleteAtomicContent, we cannot remove it due to non-editable and we
don't know whether this leaf (and this non-editable tree) are removable.
So we would like to change reason content from leaf node of non-editable to
topmost non-editable node if possible.
Also, using [Delete] key still use frame selection, so WSRunObject don't still
consider this situation yet. And actually we don't support deep complex
case (see test case) yet since Chrome doesn't remove any elements on this
test case.
Depends on D92586
| Assignee | ||
Comment 10•5 years ago
|
||
https://searchfox.org/mozilla-central/rev/35245411b9e8a911fe3f5adb0632c3394f8b4ccb/editor/libeditor/tests/browserscope/lib/richtext2/richtext2/tests/delete.py#264-267 etc are incorrect for current behaviour.
browserscope isn't active project, so there is no way to feedback this.
Depends on D92587
| Assignee | ||
Comment 12•5 years ago
|
||
| Assignee | ||
Comment 13•5 years ago
|
||
selection issue is moving to bug 1670531 since editor uses nsFrameSelection for backspace/delete.
Updated•5 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
| Assignee | ||
Updated•4 years ago
|
Updated•3 years ago
|
Comment 14•2 years ago
|
||
The remaing bugs should be handled in bug 1873155.
Updated•2 years ago
|
Description
•