Closed Bug 505112 Opened 15 years ago Closed 14 years ago

Window Not Active when starting Firefox (following upgrade to 3.5)


(Firefox :: General, defect)

Windows Vista
Not set





(Reporter: seaicmac+mozbug, Unassigned)


(Whiteboard: [CLOSEME 2011-1-1])

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv: Gecko/20090715 Firefox/3.5.1 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv: Gecko/20090715 Firefox/3.5.1 (.NET CLR 3.5.30729)


A slight problem I have noticed after upgrading to Firefox 3.5:
When I open Firefox, the window appears and loads homepage (google) as I would expect. However the window loses focus after a few milliseconds and then Firefox is no longer the active window. This then means that I have to click on the firefox window to make it become active.

The problem becomes weirder if I already have an instance of firefox open and then try to open another instance of firefox (either by clicking File>NewWindow, pressing CRTL+N, or by clicking a shortcut to the program on my desktop or start menu). If I try to open a new instance, it opens, loads google, and then instantaneously flips the focus back to the original instance of FF. Weird!

This may seem like a trivial glitch but it is irritating when I open Firefox and my cursor is not in the search for Google, which is usually what I open FF for in a hurry.

Any ideas?

Reproducible: Always

Steps to Reproduce:
1.Ensure no instances of Firefox running
2.Open Firefox and wait for it to load homepage
3.Notice that FF loses focus


1.Open an instance of firefox and wait for it to load
2.Go to a different website and wait for it to load
3.Open another instance of Firefox
4.Watch as it loads momentarily, then switches focus back to 1st instance
Reporter, are you still seeing this issue with Firefox 3.6.12 or later in safe mode? If not, please close. These links can help you in your testing.
Also, please consider using the most recent Firefox 4 beta build, your bug may be resolved there.
Whiteboard: [CLOSEME 2011-1-1]

Issue has been resolved with upgrade to 3.6.

Closed: 14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.