Mail/Newsgroup window size not remembered if larger than Xwindow size (new bug for 1.4)



15 years ago
13 years ago


(Reporter: Allan Duncan, Unassigned)


Firefox Tracking Flags

(Not tracked)





15 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.4) Gecko/20030701
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.4) Gecko/20030701

I use Gnome (1.4.0) with Sawfish (1.0.1) as the window manager, with one workspace
and 2x2 virtual desktops.  This means that I can have a window that is larger than
the 800x600 screen and jump to the off-screen portions.
Very good for mail and newsgroups where you have the list of groups on the left
pane and the list of items on the right.  Double clicking opens up an item using
all of the 800x520-odd space giving a decent chunk of text.

Up to Mozilla 1.3 this extended window would correctly reopen to the set size,
but with 1.4 it is truncated back to 800 wide.

From localstore.rdf when the wide window is closed:
<RDF:Description about="chrome://messenger/content/messenger.xul#messengerWindow"
                   width="1584" />
Note that the screenX="-800" is because the close button is only accessible from
the righthand pane.  It doesn't matter whether it is 0 or -800.

If the browser and mail is restarted then closed you get width="800".

Experimenting shows that mozilla is now over-riding the width value with
whatever the screen size X is displaying.  As can be seen from this case, this
is not always the right decision, as this may be a virtual size that is a subset
of a larger screen.

Allied to this I notice that prefs.js contains
   user_pref("mail.thread.win_width", 1584);
which is blithly ignored by the browser (1.3a and 1.4).  Should about:config be
purged of what appear to be obsolete options?

Reproducible: Always

Steps to Reproduce:
Product: Browser → Seamonkey
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:
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.