Closed Bug 29843 Opened 25 years ago Closed 24 years ago

nsHTMLEditRules::AfterEdit needs to ensure that the caret is always made visible again

Categories

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

Product:
Core
Component:
DOM: Editor
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: teruko, Assigned: mozeditor)

References

Details

(Whiteboard: (fix in hand) [nsbeta2+]) 

When you type characters more than one line and use Backspace key to delete whole characters, you will lose the caret 
in Composer.

Steps of reproduce
1. Open Composer
2. Type "aaaa" and hit return to go to next line
3. Type "bbbb"
4. Hit Backspace key 9 times to delete whole characters
5. Hit one more Backspace key

You will lose the caret.  You cannot type any characters in Composer anymore until you close Composer and
start it again.

Tested 2000030108 Win32, MAC, and 2000030113 Linux build.
m15
Status: NEW → ASSIGNED
Target Milestone: M15
moving to m16
Target Milestone: M15 → M16
*** Bug 35388 has been marked as a duplicate of this bug. ***
*** Bug 34761 has been marked as a duplicate of this bug. ***
The problem here is that we are returning prematurely from 
nsHTMLEditRules::AfterEdit() because mEditor->CollapseAdjacentTextNodes() returns 
an error.

thanks for triage! accepting bug..


marking as beta2, sould have done this before.
Keywords: beta2
Priority: P3 → P1
Keywords: nsbeta2
I checked in a fix for the problem in ollapseAdjacentTextNodes(). Adjust summary 
and leave open for bullet-proofing.
Keywords: beta2
Summary: Using Backspace will lose caret in Composer → nsHTMLEditRules::AfterEdit needs to ensure that the caret is always made visible again
Whiteboard: [nsbeta2+]
Whiteboard: [nsbeta2+] → [nsbeta2+] ETA 5/8/00
Whiteboard: [nsbeta2+] ETA 5/8/00 → [nsbeta2+]
i have fix in hand
Whiteboard: [nsbeta2+] → (fix in hand) [nsbeta2+]
fixed
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
verified in 5/26 build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.