Closed Bug 209867 Opened 22 years ago Closed 21 years ago

LeftArrow, RightArrow do not move caret correctly after delete

Categories

(Core :: DOM: Selection, defect)

defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: bzipitidoo, Assigned: mjudge)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030612 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030612 In an empty text area, type: a<Enter>b<CtrlShiftHome><Delete>c<DownArrow>d<LeftArrow><LeftArrow> Reproducible: Always Steps to Reproduce: In an empty text area, type: a<Enter>b<CtrlShiftHome><Delete>c<DownArrow>d<LeftArrow><LeftArrow> Actual Results: caret moves after 'd'. Expected Results: caret should move before 'c'.
Also a<Enter>b<CtrlShiftHome><Delete>c<CtrlEnd>d<Home><RightArrow><RightArrow> Similar to bug 88164.
Summary: LeftArrow, RightArrow do not move caret correctly → LeftArrow, RightArrow do not move caret correctly after delete
More ways to cause this bug in Mozilla 1.4 RC2. Move caret to end of text area (empty or not), then <Enter>a<ShiftUpArrow>b<DownArrow>c<LeftArrow><LeftArrow> Another case, shows up anywhere, not just at end of text: <Enter><Enter><Enter><UpArrow>a<ShiftUpArrow>b<DownArrow> c<LeftArrow><LeftArrow><LeftArrow>
May need one more LeftArrow to see the bug: <Enter><Enter><Enter><UpArrow>a<ShiftUpArrow>b<DownArrow> c<LeftArrow><LeftArrow><LeftArrow><LeftArrow> Can see the RightArrow problem by doing the above plus: d<Home><RightArrow><RightArrow>
I can't reproduce this. Brent, do you still see this problem? Prog.
After 1.4 I quit downloading Mozilla, since MNG support was removed and I want to keep MNG. The bug is present in version 1.4. This bug is not present in MozillaFirebird 0.7. I just now got Mozilla 1.6b (Linux) and tried to duplicate this bug. The bug does not happen in 1.6b with the keystrokes given. But, in 1.6b, I can see that it may still be possible to cause a problem with some other sequence of keystrokes, because the carat can be put in 2 different positions about 2 pixels apart depending on whether the carat is moved between the c and d with the right or the left arrow key. When the MNG guys get a 1.6 version with MNG included, I'll give it another shot and file another bug or reopen this (no doubt this bug is headed to the "worksforme" scrap heap) if I find a way to cause something.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.