320558 - window.focus() in Linux doesn't activate the window to accept keystrokes

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Dave Cohen]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

When calling window.focus() in a background window, it will bring the window foremost but doesn't activate it to capture keystrokes (they still go to the previous active window).

This is reproduceable in 1.0.x and 1.5. Only seen in Linux.

Reproducible: Always

Steps to Reproduce:
1. Open 2 windows, window A, and window B. Window B has a form.
2. While working in window A, an action causes the form in window B to take focus (window.focus() followed by texarea.focus()). For testing you can use a simple timeout in window B.
Actual Results:  
Window B comes foremost and a caret appears in the text box, but keystrokes still go to window A.

Expected Results:  
Window B comes formost and keyboard input goes into window B.


Running RedHat 9, KDE window manager.

Comment 1

[zug_treno]

Maybe related to Core bug 155436?

Comment 2

[Dave Cohen]

It looks like it could be related. However the difference with this bug is that if I manually click into window B the window will take focus and everything continues to work as expected (with #155436 the window never properly regains focus).

Comment 3

[Tyler Downer [He/Him]]

This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode

Comment 4

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.3 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.