Closed Bug 85095 Opened 25 years ago Closed 25 years ago

Deleting rest of <li> deletes all of it

Categories

(Core :: DOM: Editor, defect)

defect
Not set
major

Tracking

()

VERIFIED FIXED
mozilla0.9.2

People

(Reporter: BenB, Assigned: mozeditor)

Details

(Keywords: dataloss, regression, Whiteboard: (I believe 64847 patch fixes this))

Reproduction: 1. Create new Mail in HTML mode 2. Open new <ol> 3. Create 3 <li>s with text 4. Set caret in the second <li> in the middle of its text 5. Select text until end of <li> with SHIFT-End (and Cursor-Down, if you have multiple lines) 6. Delete it by hitting Delete key. Actual result: - All of the <li> is gone. - No undo is possible Expected result: - Only the selected text, i.e. the second part of the <li>, is deleted - Undo is possible Build: Mozilla 0.9.1, Linux, my own build with gcc 2.95 and O2. No source modifications made. Importance: During writing one mail, I already lost 3 or more paragraphs. Dataloss.
I can't reproduce this on build 2001060712 on Macintosh. Describe it more.
I'm pretty sure that this is a regression, as often as I run into it and I never did before. Importance (continued): I run into it all the time, when I decide that the last word I wrote was inappropriate and want to delete it - I end up loosing the whole paragraph (=<li>).
Keywords: regression
> 4. Set caret in the second <li> in the middle of its text Sorry, this is wrong. The bug only happens for the last <li> and only if that <li> always has been the last <li>.
I beleive this is fixed by one of my other patches. probably 67847.
Status: NEW → ASSIGNED
Whiteboard: (I believe 64847 patch fixes this)
Target Milestone: --- → mozilla0.9.2
marking fixed. Ben, I could never exactly reproduce the problem you saw. But I did get other problems, which are now fixed. Try a build on/after 6/13 and see if it works for you.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
i verified that this is not happening anymore (if it ever happened) on trunk builds 0618 all plfs. Ben, pls double chek.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.