284008 - Text Input Field corrrupts (displayed) text & cursor position

Status: RESOLVED EXPIRED

(Toolkit :: Form Manager, defect)

Description

[George Ellenburg]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/125.5.6 (KHTML, like Gecko) Safari/125.12
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1

Go to any page that has a text-input field.  Perhaps Slashdot or even this bug report page.

Now, begin typing text.  Any text will do.  The closer the cursor gets to the right of the text-input page, 
the more corrupt the text appears.

This has been a consistent bug since Firefox 0.8 but I haven't reported it until now in the hopes that it 
would have been caught during QA.

It appears to be a problem specifically with spaces or the space-bar, and it only appears to affect multi-
line text boxes (with vertical scroll-bars).  Haven't really noticed it appearing in a text-input box with a 
horizontal scroll-bar so I'm not sure about that one.

To reproduce this bug, start typing.  Any text will do.  But, don't just enter a long, contiguous string 
without any spaces because that won't show the bug at all.

To really see the bug in action, enter somehting like 
"0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4..." and continue entering one character followed by a 
single space until the cursor gets all the way to the right.

As your cursoe moves across the text input-box, you'll notice that it will "creep" to the left a bit.  The 
farther to the right then the farther to the left the cursor will creep, eventually overwriting the pressed 
key and even moving so far to the left that the cursor precedes the displayed character.

The wider the text-input box the more pronounced this bug appears also.

I have not noticed this behavior on either LInux or Windows, but I have noticed this behavior just now 
with the latest Mozilla 1.8b1 build that I just downloaded so this doesn't appear to be a bug in Firefox 
per se', but in the Gecko rendering engine.  I couldn't find an easy way to report bugs in Gecko so 
hopefully you will move this bug to it's proper location.

Reproducible: Always

Steps to Reproduce:
See bug details.
Actual Results:  
See bug details.

Expected Results:  
Text entered into an input box should not become corrupted, and the cursor position should always 
stay to the immediate right of the character entered (and displayed) for western languages.

Comment 1

[Daniel M Maguire]

I have noticed the same bug. I find it particularly troublesome when going to
sites requiring a password (usually encrypted). I am running windows xp sp2 on a
dell dimension 4500s.

Comment 2

[riscky]

*** Bug 286684 has been marked as a duplicate of this bug. ***

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.