Open Bug 1016372 Opened 8 years ago Updated 2 years ago

Editor: spaces lost when deleting text flanked by empty inline tags (contenteditable/designmode)


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

29 Branch
Windows 8.1




(Reporter: cacyclewp, Unassigned)



(1 file)

1. Use the following code in an iframe in designmode or in an contexteditable container: "Before <span></span>Delete me<span></span> After"
2. Select the "Delete me" text, either using only the mouse or using the mouse and the cursor buttons so that the selection is extended from within the text
3. Push the delete key or the backspace key to delete the selected text
4. Both adjacent spaces should stay, this works as expected in Chrome
5. Bug: one of the adjacent spaces gets erroneously deleted (Mozilla/5.0 (Windows NT 6.3; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0)
6. It works correctly when selecting the text with the cursor keys coming from outside the text

This is a really confusing bug when editing online content such as Wikipedia using the wikEd editor.
I am able to reproduce the problem as described on Win 7 x64 with:
- Firefox 30 Release Candidate - Mozilla/5.0 (Windows NT 6.1; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0 - BuildID: 20140603140158
- Latest Firefox 31 Aurora - Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0 - BuildID: 20140604004003
- Latest Firefox 32 Nightly - Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:32.0) Gecko/20100101 Firefox/32.0 - BuildID: 20140602030202

The also reproduces on Firefox 4.0.1, so it's not a regression.
Component: General → Editor
Ever confirmed: true
Product: Firefox → Core
Version: unspecified → 29 Branch
This bug is still present in 52.0.1 (Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0) and is still a problem. Anybody willing to work on this?
Priority: -- → P3

Bulk-downgrade of unassigned, untouched DOM/Storage bug's priority.

If you have reason to believe, this is wrong, please write a comment and ni :jstutte.

Severity: normal → S4
Priority: P3 → P5
You need to log in before you can comment on or make changes to this bug.