Closed Bug 98260 Opened 24 years ago Closed 24 years ago

delete doesn't merge lines together

Categories

(Core :: DOM: Editor, defect)

defect
Not set
normal

Tracking

()

VERIFIED FIXED
mozilla0.9.7

People

(Reporter: sujay, Assigned: mozeditor)

References

Details

(Whiteboard: EDITORBASE; fixinhand; patch in 99523)

1) launch netscape 2) launch composer 3) insert text on first line 4) hit carriage return 5) insert another line of text 6) place caret before first char of first line 7) hit bullet list 8) click end of first line 9) hit "Delete" key observe caret moves down to the second line and deletes first char. expected: second line should get appended to the first line and caret should stay on first line. Another scenario: a) add 2 x 2 table b) click in any cell c) repeat steps 3 thru 9 above observe: caret locks up, doesn't delete anything expected: second line should get appended to the first line and caret should stay on first line.
096
Status: NEW → ASSIGNED
Summary: delete → delete
Target Milestone: --- → mozilla0.9.6
this is "forward delete", right?
Summary: delete → delete doesn't merge lines together
Whiteboard: EDITORBASE; 5 days;
*** Bug 98614 has been marked as a duplicate of this bug. ***
adding QAHP
Whiteboard: EDITORBASE; 5 days; → EDITORBASE; 5 days; [QAHP]
*** Bug 98560 has been marked as a duplicate of this bug. ***
097
Target Milestone: mozilla0.9.6 → mozilla0.9.7
Whiteboard: EDITORBASE; 5 days; [QAHP] → EDITORBASE; fixinhand; patch in 99523
fixed by 99523 checkin
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
On Win 2k using build 2001121803, I am seeing a similar issue. Using the same steps, I see that after step 9, the caret jumps down to the second line, but does not delete the first character. If I put the caret back up at the end of the first line, and then hit delete again, it will append the two lines together. I am reopening this bug.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
WORKSFORME. There is a known issue with my recent deletion work that you may be seeing. If the content that would be pulled into an adjacent block is _not_ a text node, then you see the behavior you describe. I have opened 115900 to cover that.
Status: REOPENED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → FIXED
Verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.