Closed Bug 249388 Opened 20 years ago Closed 19 years ago

Windows size not restored correctly on restart

Categories

(SeaMonkey :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: biguniversejr, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040614 Firefox/0.9
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040614 Firefox/0.9

This happens to me at least once (if not more times) daily but I don't know if I
can reproduce it.  One out of 5-6 times, when I exit Firefox (and Mozilla 1.6 in
the past, for that matter), the window size is not restored to the same size I
exited the browser at.  For example, say I had the window "restored down" to
400x500 and it was the last browser window that I exited.  The next time I open
the window, it is not restored to 400x500 but closer to the maximized size
(except a few pixels less and not in maximized mode, that is, I have the
minimize, maximize and close buttons on the top right).

This is a bit annoying, as I have to always resize the window to the restored
size I like to have it.  This used to happen to me in Mozilla 1.6 all the time
but it apperently hasn't been fixed.

Thanks.

Reproducible: Didn't try
Steps to Reproduce:
Product: Browser → Seamonkey
Not able to reproduce with Mozilla/5.0 (Windows; U; Windows NT 5.0; es-ES;
rv:1.7.5) Gecko/20041108 Firefox/1.0. Could you test with a newer build?
Same problem happened, it cannot be reproduced easily, incidents are sporadic.

Firefox sometimes fails to remember the size of "restored down" window and when
you click on "restore down" button it makes the window only  a few pixels
smaller than the maximized window.

The problem is reported on a custom build, but it also happens on Firefox 1.0
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041109
Firefox/1.0 (MOOX M2) 
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/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.