243782 - Cursor blinks but you can't type; click into field and typing results in text in another field

Status: RESOLVED FIXED

(Core :: Layout: Form Controls, defect)

Description

[Carsten Otto]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040416 Firefox/0.8
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040416 Firefox/0.8

Hello!
Sometimes, a lot less than always, I have following phenomenon on the given site:
the cursor blinks in the first field (Kontonummer), but when I start to type
either nothing happens or the text appears (***) in the PIN field. When nothing
happens and I click on the first field, where I want to put my text, it
sometimes works and sometimes the text appears in the field below.
Please tell me how to give more precise information, if you don't understand.

Reproducible: Sometimes
Steps to Reproduce:
1. Visit the site several times
2. Try to write into the first field
3. Watch the cursor

Actual Results:  
Text appears in wrong field or nothing happens

Expected Results:  
Text should appear in the field where the cursor blinks in

Comment 1

[Martijn Wargers (dead)]

This bug is almost the same as bug 241942.
Removing the ESM patch from bug 198153 solves this bug (as the other bugs
mentioned in bug 241942).

However, there is a separate issue:
It is difficult to get a blinking caret in the password textbox.
Clicking with the mouse from the first textbox to the password textbox you won't
get to see the caret blinking (although you can type text in the password textbox).
First, somewhere clicking in the frame and then clicking inside the password
textbox and you'll see the caret blinking.

Comment 2

[OstGote!]

Confirming the phenomenon. On my first attempt it was as described, all further
attempts work. Mozilla trunk build 2004051108 WinNT4.

Comment 3

[Martijn Wargers (dead)]

Well, I'm marking this bug as fixed because of the fixing of bug 241942.
I don't see it at least not anymore with builds after the fixing of that bug.
For the other issue I mentioned in comment 1, I filed bug 246576.