Closed Bug 21346 Opened 25 years ago Closed 25 years ago

Insertion point occasionally horked when typing.

Categories

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

x86
All
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: trudelle, Assigned: mozeditor)

References

()

Details

Using today's comm opt bits on Linux (RH 6.0):
When typing in a multi-line edit field (specifically, the Enter Bug form), the
caret will occasionally take a wrong turn, so that I'll suddenly be entering
text in the middle of the previous line, beginining of the current line, or
other incorrect location.  This happens when I'm just hitting alphanumeric keys
and backspace, not using the cursor keys nor the mouse.  I can't reproduce it at
will, but it has been happening once or twice on nearly every bug I file.

May be timing related, as I (it just happened again!) am a fairly fast typist
but am running on a P166 with an Messenger IMAP window open (using biff).

assigning to jfrancis per beppe.
Target Milestone: M13
setting to M13
I think this might be a dup of a bug buster has on his plate, but i can't seem
to find it today.

Here's how to reproduce this bug ...

1. Start with a blank Gfx text area or blank PlainText compose window.
2. Type "This is a" and hit return.
3. Click the mouse to the right of the 'a' on the first line to place the caret
at the end of the line. Note: Don't click right over the 'a' to place the caret,
click a little farther to the right of the 'a'.
4. Now type " test".
5. Now place the caret just before the "T" on the first line.
6. Type "a", then hit the backspace key.

Notice how the caret jumps to just after the "a"?
As I reported, no clicks or cursor movement was involved.  Also, the caret
jumped 30-40 characters, and sometimes up a line.
Status: NEW → ASSIGNED
i'm looking into this now...
Blocks: 21545
Today I'm seeing the backspace key leapfrog over several letters without
deleting them.  Seems like it could be the same problem.
OS: Linux → All
Marking all as it happens with WinNT also, currently build 1999122108, but has
been happening for a while now.
*** Bug 22443 has been marked as a duplicate of this bug. ***
*** Bug 22851 has been marked as a duplicate of this bug. ***
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
fixed
Status: RESOLVED → VERIFIED
verified in 12/6 build.
You need to log in before you can comment on or make changes to this bug.