246981 - new windows and/or new window's URL bar won't take focus, browser only shows "Firefox" menu

Status: RESOLVED WORKSFORME

(Firefox :: Keyboard Navigation, defect)

Description

[Jason Sonnenschein]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-us) AppleWebKit/125.2 (KHTML, like Gecko) Safari/125.8
Build Identifier: Can't Get browser to run correctly... it's version 0.9, downloaded 6/15/04

Brower sometimes comes up and only has "Firefox" menu... no File, edit, etc.  By clicking back and forth 
to other running applications, I sometimes can get the browser to take focus, but when I have Firefox 
open a second window, anything I type in the URL bar goes to the URL bar of the first window that 
Firefox opened... NOT the window I'm typing in.

Reproducible: Always
Steps to Reproduce:
1. Run browser
2. Open a New (second) browser window
3. Click on URL bar of new window and type in it.
Actual Results:  
text I typed went to the URL bar of the first window

Expected Results:  
Text should have shown up in the URL bar of the window that had focus.

I'm running on OS 10.3.4.  When this bug appeared, I removed my whole ~/Libraries/Application 
Support/Firefox directory... this did not fix the problem.  I also quit the Application "Virtual Desktop 
Pro," which I usually run.  Neither of these actions fixed the problem.  I run the 3rd party system 
extensions "APE Manager" and "Menu Meters."  Otherwise, my system is pretty standard.

Comment 1

[Jason Sonnenschein]

Here's the Build Identifier string from the browser
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040614 Firefox/0.9

Comment 2

[Joseph Hall]

I see this in the 0.9 release... it's a pain in the butt.  I saw similar
behavior with the 0.9rc1 but this focus problem seemed fixed in the latest
nightly that I had downloaded then.  I just checked the latest nightly and this
problem is there too... I wish I had jotted down the build number of the nightly
I had where this focus problem was fixed, but I did not.

Comment 3

[John Lianoglou]

It seems that Firefox's focus management gets screwy when CodeTek's virtual
desktop is also running.  One sure-fire to reproduce such a focus problem is to
view the source of any web page, then try to close the window using cmd-w.  Not
only will it not close, but focus is still lost when you return to the web
page... try typing cmd-l to get to the location text field; that won't work either.

In circumstances that I don't know off-hand how to reliably produce, I've
experienced circumstances under which cmd-w would close tabs in background
browser windows!

The work around to this is to switch to another application, then back to
firefox.  Focus will behave normally again, until some other action triggers the
problem to re-emerge.  It's just a simple cmd-tab, cmd-tab to fix... but quite
painful to close saved tabs unintentionally.  :)

NOTE: The reason I suspect the problem to be with firefox rather than CodeTek's
Virtual Desktop is that no other programs on my system behave in this way.  From
photoshop to XCode, focus handling behaves as "expected."

Comment 4

[Joseph Hall]

(In reply to comment #3)
> It seems that Firefox's focus management gets screwy when CodeTek's virtual
> desktop is also running.  One sure-fire to reproduce such a focus problem is to
> view the source of any web page, then try to close the window using cmd-w.  Not
> only will it not close, but focus is still lost when you return to the web
> page... try typing cmd-l to get to the location text field; that won't work
either.

I can confirm this... I am also running CTVD v 3.1 (CodeTek's Virtual Desktop)
this behavior seems to dissappear if I kill CTVD.  That's not much of a solution
since it's my window manager.  I also see no other behavior like this in any
other app.

Comment 5

[Jason Sonnenschein]

Granted... a workaround, not a fix.  But I just found a GPL'ed (free) virtual
workspace manager that's pretty much feature equivalent to Virt. Desktop Pro

http://wsmanager.sourceforge.net/

Comment 6

[Dan Creswell]

(In reply to comment #2)
> I see this in the 0.9 release... it's a pain in the butt.  I saw similar
> behavior with the 0.9rc1 but this focus problem seemed fixed in the latest
> nightly that I had downloaded then.  I just checked the latest nightly and this
> problem is there too... I wish I had jotted down the build number of the nightly
> I had where this focus problem was fixed, but I did not.

I'm still seeing this problem in the Preview release.  I too am running Codetek
Pro Virtual Desktop.

Comment 7

[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 8

[Fabio Russo]

dup of bug 283050 in its original formulation, but not in the issue with
"CodeTek's virtual desktop".

Comment 9

[Samuel Sidler (old account; do not CC)]

Jason or Dan, does this still occur using the latest version of Firefox (1.5)?

Comment 10

[Dan Creswell]

(In reply to comment #9)
> Jason or Dan, does this still occur using the latest version of Firefox (1.5)?
> 

Went away a while ago - should have said, sorry.

Comment 11

[Samuel Sidler (old account; do not CC)]

Resolving WFM since we don't know which checkin fixed this.

Thanks Dan!