471095 - Browser always opens new window to "maximum" window size even if dismissed from a reduced setting

Status: RESOLVED DUPLICATE of bug 232919

(Firefox :: General, defect)

Description

[Mike Smith]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.0.5) Gecko/2008120121 Firefox/3.0.5
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.0.5) Gecko/2008120121 Firefox/3.0.5

When dismissing the FF window (click the red x button), leaving the engine application running, FF always opens a new window (when FF dock icon is clicked) to a full-screen window, regardless of how the window was previously sized.  It is then necessary to click "best size" (green + button) to restore to last window dimension.  Especially annoying with a wide-screen monitor, as the full-size can be far too large a spread with some pages. OS X version 4.11.  Could be some vestigal config datum or conflict from a previous FF installation??

Reproducible: Always

Steps to Reproduce:
1.Start FF 3.x, adjust desired window size
2.Click red x to dismiss main window with engine still running. (This is different from minimizing a window with orange - button)
3.Clock FF dock icon to open new FF window (icon is always in dock)
Actual Results:  
When a new window opens, it fills the entire screen ("maximized" condition).  On a wide-screen monitor the problem is especially annoying, and the green + button must be clicked to set desired size.  My typical use is to click the red x to remove the window from the desktop and dump any open tabs, then click the FF dock icon to open a new window when needed.

Expected Results:  
It would be very helpful for FF to "remember" the last used size from window to window so that new windows are the same size as the last window used.

I can't find any config key to control new window size (not that there necessarily isn't one; I just haven't found it!), but there could be an add-on or old config key from a previous FF version, perhaps.  FF 3.x was installed as an upgrade from 2.x (can't remember seeing this problem in 2.x).  Possibly affected by some add-on?  Some add-ons are MR Tech Toolkit, Tab Mix Plus...