Closed
Bug 144784
Opened 23 years ago
Closed 23 years ago
cursor moves while typing
Categories
(Core :: DOM: Editor, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: davidmaxwaterman, Assigned: kinmoz)
Details
This just happened to be for the first time.
I was composing an email and while I was typing, the cursor moved to a different
line, corrupting my message and causing me to have to try again.
Most occurances of this behaviour were sort of random - ie if I was typing
something, the cursor might suddenly move, but clicking the cursor back to where
I wanted it meant that I could continue typing there.
Hoever, there was one position in the email where, if I positioned the cursor
there, as soon as I hit a key, the cursor moved to another place - it just like
above - but clicking the cursor back to the correct position and hitting a key
(to continue typing) would result in it consistently moving back to the wrong place.
It seemed like the place the cursor moved to was always the same place, if
that's any help. The place the cursor moved was consistent, but when it did it
generally wasn't.
I can't really see what you can do about this, because it is almost certainly
not consistently reproducable, but it needed to be logged anyway (IMO).
Comment 1•23 years ago
|
||
reassign to editor
Assignee: ducarroz → kin
Component: Composition → Editor: Core
Keywords: mailtrack
Product: MailNews → Browser
QA Contact: esther → sujay
Comment 2•23 years ago
|
||
uhh.. does this still happen on 1.1beta?
Reporter | ||
Comment 3•23 years ago
|
||
I use the nightly builds, and I haven't had this happen for a long time. I have
moved platforms though (->Mac OS X, from IRIX and RH Linux).
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Max, if you ever run into this situation again, try saving the doc you are
composing and attach it here so we can get an idea of what the content looks
like at the time this happens.
Comment 5•22 years ago
|
||
w4m with 2003.04.10 on linux rh8.0 --reopening if you see this again with a
recent trunk build.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•