Open Bug 685799 Opened 13 years ago Updated 18 days ago

Delete doesn't work on the last contenteditable=false element nested in a contenteditable=true element

Categories

(Core :: DOM: Editor, defect)

7 Branch
defect

Tracking

()

People

(Reporter: ioana_damy, Assigned: m_kato)

References

(Blocks 2 open bugs)

Details

(Whiteboard: [h2review-noted])

Attachments

(1 file)

Attached file reduced test case
Mozilla/5.0 (Windows NT 6.0; rv:7.0) Gecko/20100101 Firefox/7.0
Mozilla/5.0 (X11; Linux x86_64; rv:8.0a2) Gecko/20110907 Firefox/8.0a2
Mozilla/5.0 (X11; Linux x86_64; rv:9.0a1) Gecko/20110831 Firefox/9.0a1

STR:
 1. Open the attached test case.
 2. Place the caret in front of the comma before the last span.(the caret cannot be placed right before the span because of bug #685452)
 3. Press the Delete key twice.

Expected Results:
 The first key press deletes the space before the last span and the second one deletes the last span.

Actual Results:
 The last span (blue letter) cannot be deleted.

Workaround:
 Select the last span then press Delete.
FTR/note2self: this bug is related to layout/generic/nsSelection.cpp.
nsFrameSelection::MoveCaret returns NS_ERROR_FAILURE when trying to reach the edge of the editable <div> with cursor keys.
See Also: → 1452517
Assignee: nobody → m_kato
Depends on: 1484593
Depends on: 1484602
This is still the case in version 62, and probably related to issue 1267897
See Also: → 1509650
Whiteboard: [h2review-noted]
Severity: normal → S3

The severity field for this bug is relatively low, S3. However, the bug has 3 duplicates.
:m_kato, could you consider increasing the bug severity?

For more information, please visit auto_nag documentation.

Flags: needinfo?(m_kato)

The last needinfo from me was triggered in error by recent activity on the bug. I'm clearing the needinfo since this is a very old bug and I don't know if it's still relevant.

Flags: needinfo?(m_kato)

I can still reproduce the issue with STR from comment 0, using latest Nightly 125.0a1. I've tested on Win 11.

You need to log in before you can comment on or make changes to this bug.