Closed Bug 516168 Opened 16 years ago Closed 6 years ago

Browser window does not get focus when launching in Snow Leopard

Categories

(Firefox :: Shell Integration, defect)

x86
macOS
defect
Not set
minor

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: spiralman, Unassigned)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 After upgrading to OS X 10.6, when I launch Firefox, the browser window does not get focus. This means that shortcuts like Command-L do not work until I click on the window. The application itself, though, does have focus (the unified menu bar shows the Firefox menu). Reproducible: Always Steps to Reproduce: 1. Launch Firefox 2. Observe focus of main browser window. Actual Results: The main browser window does not have keyboard focus. Expected Results: The main browser window should have keyboard focus.
I can confirm this as well. My problem is exactly the same as above. Additionally, if I click on a link in an email message (using Apple Mail) Firefox will launch but remain unfocused and under Mail's window.
Just discovered bug # 515571. I will disable growl on my Snow Leopard install and see if it's the cause of my problem and report back.
After going to system prefs and opening the Growl prefs I clicked on the "Stop Growl" bug (and unticked the checkbox to make Growl not launch at startup) and my focus problem was solved. It appears it's a Growl problem, not a Firefox problem.
Disabling Growl also solved the focus issue for me. However, the problem still seems to be specific to Firefox (or, at least, not globally present, as other apps launch just fine).
I've been experiencing this issue for some time and uninstalled Growl prior to the release of 1.2. However, faced the same problem - again - once the new version of Growl was reinstalled. Now that Firefox 3.5.4 has been released I'm dismayed to find that Growl coders say it's Mozilla's problem and Mozilla has yet to address it. I don't know what is "unconfirmed" but this issue is discussed here (I posted a bug notice over a month ago, with several links to my thread) and at Growl, so it's not an isolated problem. Hope someone will be able to track down the cause and at least suggest a remedy. Somed(a)y. :)

Bug 777409 removed Growl support from Firefox (as notifications were built into Mac osx). So this should no longer be an issue. If it is, please can you file a new bug with details of OS/Versions.

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.