433675 - Firefox main window moves to -32000/-32000 position when <ALT>+<TAB> -bing

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Axel]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14

Sometimes when I hit <ALT>+<TAB>, Firefox moves itself to somewhere where I can't see it. After closing Firefox from the Task Bar and looking into localstore.rdf, I find an entry like

 <RDF:Description RDF:about="chrome://browser/content/browser.xul#main-window"
    width="86"
    height="36"
    screenX="-32000"
    screenY="-32000"
    sizemode="normal" />


Reproducible: Sometimes

Steps to Reproduce:
<ALT>+<TAB>, while some other application just opens a new main window.
Actual Results:  
see above.

Right-clicking the anchor at the Windows Task Bar and selecting "Maximize" will bring the window back. Selecting "Restore" afterwards will "hide" the window again then.

Expected Results:  
Firefox should display as usual.

Comment 1

[Régis Caspar]

I experiment that since a few days (2 I think) with nightly builds.
After each update I apply when Firefox restarts, the main window is out of any of my screens (i've 2). localstore.rdf as in comment #1
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2a1pre) Gecko/20090722 Minefield/3.6a1pre (.NET CLR 3.5.30729) ID:20090722042136

Leaving as UNCONFIRRMED because of the reporter FF version

=> qawanted, major (user needs to edit or delete localstore.rdf to use Firefox!)

Comment 2

[Axel]

I can reproduce this behaviour with FF 3.5.3 on Windows 7 every time:

Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3

It's now not even possible to re-maximize the window because Windows 7 implements a new Jump List feature, disabling the usual context menu.

Steps to reproduct:

* Have only FF window opened.

* Hold the <FLAG> key pressed and quickly press <TAB> twice.

Comment 4

[therube]

I can confirm the -32000 positioning as reflected in localstore.rdf with SeaMonkey, Windows 7 x86.

Mozilla/5.0 (Windows NT 6.1; rv:2.0b5pre) Gecko/20100822 SeaMonkey/2.1b1pre

I cannot confirm steps to reproduce.  But before figuring out what was going on (I had always called these "dead windows"), my suspicion was that it had something to do with Session Restore?

In my case, I have 41 or so windows (with an untold number of tabs) open.  The majority of my windows display properly, but a handful among these are these "dead windows".

Before figuring this out, I also had a suspicion that the dead windows were outside the viewable area.  Using http://www.nirsoft.net/utils/winexp.html I can confirm that each "dead window" that I have has its' positioning (Left | Top) at -32000 -32000.  Viewable windows are at -4 -4 or somewhere around that. Width & Height for all windows are in normal ranges.  "Window State" for all these dead windows shows as Minimized.


@Axel, <Ratty> therube: well according to that article you can Shift+Right-click on a taskbar button: Show the window menu for the program (like XP does).

Comment 5

[therube]

<NeilAway> therube: interesting... -32000 is the position of minimised windows...
NeilAway: ah, you're right. any (not just Mozilla) minimized window gets a -32000


> so wonder if ... last window closed happened to be minimized that would set -32000 in localstore.rdf or something like that?

Haven't been able to figure that angle out (yet?).

Comment 6

[Tyler Downer [He/Him]]

Reporter, are you still seeing this issue with Firefox 4.0.1 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles

Comment 7

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 4 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). Also, ensure you have the most up to date graphics drivers, operating system updates, and plugin versions (flash, java, etc). If you continue to see this issue with the newest Firefox and a new profile, then please comment on this bug.

Comment 8

[Axel]

Hi, I tried to reproduce the problem with FF4 but couldn't reproduce it yet.

So I regard this issue as fixed now.

Thanks for taking the time.

Comment 9

[Wayne Mery (:wsmwk)]

Axel, thanksn for the update