all textfields become keyboard inactive after switching focus with alt+tab



14 years ago
13 years ago


(Reporter: Mikko Häkkinen, Unassigned)


Windows XP

Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113

This may be a problem only reproducible on WinXP.

Many textfields - regardless of being web forms or a mail composition field -
become keyboard inactive when switching focus from window to another and back.
This happens always with this version (1.6). Haven't tried 1.7b. There is also
some other problems, e.g. with cursor buttons and multiple browser windows.

This problem may already be in the bug database because there were few similar
bugs but didn't feel like they were exactly the same bug. This bug may also be
repaired because I'm using Mozilla 1.6 and don't know the situation with 1.7b.

Reproducible: Always
Steps to Reproduce:
1. Open a webpage with a form or a mail composition window.
2. Start writing a message.
3. Alt+Tab to switch focus to another window. Alt+Tab to switch focus back.

Actual Results:  
There is a cursor in a textfield but you can't write into it.

Expected Results:  
You should be able to write into the text field where the cursor is.

Comment 1

14 years ago
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040318 Firefox/0.8


Comment 2

14 years ago
Works for me using Firefox 0.8 on Win2k.

Reporter: is this still happening to you?
Maybe it's another focus related problem, like bug 124750.
Product: Browser → Seamonkey
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:
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.