71402 - window size and placement are not remembered

Status: NEW

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Jonathan S Abrams]

The mail window does not always spawn in the same location, and with the same
size, as set in a previous mozilla session.

Steps to reproduce:  Launch Mozilla, open the mail window, and position it and
size it as desired.  Quit Mozilla, and relaunch Mozilla.
What happens:  The mail window size and location is not the same.
What should have happened:  The mail window should have been positioned the way
it was in the previous session and with the same size.

OS:  Macintosh 9.1
build id:  2001030808

Comment 1

[lchiang]

don't we have a bug on this already?

Comment 2

[Jonathan S Abrams]

You might, but the search engine didn't turn anyting up.

Comment 3

[Ninoschka Baca]

Bug# 24363 was logged. It became a dupe of bug# 31086 which states that the Mac
version no longer has the problem and for linux it won't be fixed due to window
management issues.

Build 2001-03-08-08: Mac 9.04
Using this build I am unable to duplicate the reported problem. The window
position and size are remembered after quitting and restarting in a variety of
scenarios. I'll find a Mac 9.1 system and try again.

Jonathan: Is the Mozilla browser window size and position remembered?

Comment 4

[Ninoschka Baca]

Build 2001-03-08-08: Mac 9.1
Can't reproduce the problem, window size and placement is being remembered.
Are there any other steps that could make a difference?

Comment 5

[Jonathan S Abrams]

Browser window size and placement are remembered.  I can be more specific in
that the mail window will always appear as covering my entire screen.
Could it be a preferences issue (as in corrupt preferences)?

Comment 6

[(not reading, please use [e-mail] instead)]

it's not remembered in prefs, it is remembered in localstore.rdf.

in mail3PaneWindowVertLayout.xul, messenger.xul, and messageWindow.xul
(alternative 3 pane, normal 3 pane, and stand alone mesage window) we have this:

persist="width height screenX screenY sizemode"

so we are attempting to persist location and size.

there is a bug where localstore.rdf doesn't always get written out.  (it's
current assigned to me.)

are you only using the mail window, or are you using mail and browser?
(if you are only using the mail window, you are probably seeing that bug.)

Comment 7

[Jonathan S Abrams]

I'm using both browser and mail at the same time.  The problem is only with
mail, and it occurs every time I launch Mozilla.  I'll try it with just mail open,
and let you know if the problem goes away.

Comment 8

[Jonathan S Abrams]

I went into Edit-->Appearances, and set it so that only mail opens up at launch.
 Still not remembering mail window size.

Comment 9

[(not reading, please use [e-mail] instead)]

sorry for not being clear.

if you *only* launched mail and quit, this might have been a duplicate of #64000.

since you are seeing the problem when you launch both mail and browser (in the
same session) it's something else.

accepting.

Comment 10

[Jonathan S Abrams]

It sure would be nice if this could be fixed.  It's such a drag (pardon the pun)
to have to reposition windows every time I use Mozilla.

Comment 11

[Jonathan S Abrams]

This problem still exists with build 2001090408 and OS 9.2.1.  I have noticed
now that it is not only the mail component, but all of Mozilla that no longer
remembers preferences.  

This bug was, for a while, preventing me from getting the "Go" button to stay in
the browser toolbar.  That, coupled with bug 90337, probably qualifies it as a
blocker.  However, since  I was able to coax the "Go" button back, I'm
refraining from marking it as such for the moment.

In the interim, updating keyword to 0.9.5, since 0.9.4 is on the horizon.

Comment 12

[louis bennett]

system also doesn't remember if you've minimized the bottom pane.

Comment 13

[Brad Tiffany]

To reproduce, do this.  Have a browser window open if you like (to rule out the
bug Seth mentions).  Open Mail & Newsgroups from the tasks menu.  Click the zoom
box to maximize the 3-pane window.  Close the window.  Choose mail & newsgroups
again.  Resize the window manually (not with the zoom box!) and close it. 
Choose mail & newsgroups again and note that you're still stuck with a maximized
window.  Repeat to your hearts content.  Note that clicking the zoom box again
and closing the window will fix the problem, but by now the user has probably
forgotten that he or she maximized the window last week.  Looks like the generic
mac window maximizing bug 55081.

Comment 14

[Filip]

I do have the same problem with Mail client and Compose new mail window size.
Running RC1(build 20020417), Linux Mandrake 8.2. 

Comment 15

[Peter Lairo]

Could you please change the summary of this bug to:
  "Mail/News window size & position not remembered (Mac/Linux)"

because the current summary sounds too much like the TRACKING bug 145941
  "All resizable/movable windows should remember user selected size/position"

Comment 16

[corwyn]

Problem exists in build 2002061104 for Windows.
Issue did not exist in 1.0

Comment 17

[Jimmy]

I'm using build 2002091014 browser only on a windows 2000 system. And I have
this same problem with size and placement.

Comment 18

[Simon Paquet [:sipaq]]

This bug is targeted at a Mac classic platform/OS, which is no longer supported
by mozilla.org. Please re-target it to another platform/OS if this bug applies
there as well or resolve this bug.

I will resolve this bug as WONTFIX in four weeks if no action has been taken.
To filter this and similar messages out, please filter for "mac_cla_reorg".

Comment 19

[Stefan Borggraefe]

WFM with build 20030912 on Windows XP. Can anyone still reproduce this?

(Note: This doesn't work on Linux intentionally, see bug 31086.)

Comment 20

[Jonathan S Abrams]

This problem no longer exists with build 2003012108 on Mac OS 9.  I have yet to
try it in OS X, and won't for a while.  Could someone else confirm its fixed in
OS X?

Comment 21

[John Maddox]

This also happens in Mozilla 1.4 and Firefox 1.0 when running under SOlaris 8 
and CDE.  When using GNOME the screen size preferences are read from 
localstore.rdf

Comment 22

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 23

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 24

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 25

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 26

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 27

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 28

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420

Comment 29

[Karsten Düsterloh]

Size is remembered, position is not (tested under KDE).