198874 - Windows are persistently maximized after maximizing them once

Status: RESOLVED DUPLICATE of bug 198284

(Core :: XUL, defect)

Description

[Ari Pollak]

This started happening with Mozilla 1.3b/1.3. If you maximize a window (browser,
mailnews, etc.), any subsequent spawning of that same type of window will be
maximized, even if you un-maximize the window before closing it. I doubt this is
the behavior wanted in Bug #32148 - window maximization is now TOO persistent.

Comment 1

[Ken Snider]

-> XP Toolkit/Widgets.

I'm pretty sure this is a dupe of bug 192042 - it looks like this may be a valid
testcase for that bug..

Comment 2

[Stephan Jaensch]

FWIW, I can confirm this with Mozilla 1.3 on Debian Linux (unstable). A
workaround if you're using KDE: change the window to the desired height/width,
right-click the title bar and select "Store Window Settings".

Comment 3

[Dave Sherman]

I can confirm this running Mozilla 1.3 on Mandrake Linux 9.1. I will try the
workaround described by the Debian user, since it is KDE functionality and that
is what I am using for my desktop.

Comment 4

[John Wright]

Confirming on Debian's 1.3-4 build of Mozilla.  If you maximize a Navigator or
Mail/News window, even if you restore it before closing it, its sizemode becomes
"maximized" in localstore.rdf:

  <RDF:Description about="chrome://navigator/content/navigator.xul#main-window"
                   width="854"
                   height="587"
                   screenX="0"
                   screenY="0"
                   sizemode="maximized" />

The next time you open that type of window, it starts in its maximized state,
and un-maximizing it doesn't actually restore to the values in localstore.rdf. 
Manually changing any instance of 'sizemode="maximized"' to 'sizemode="normal"'
in localstore.rdf makes it behave properly.

So not only is Mozilla forgetting to change the sizemode to "normal" on a window
that has been restored from its maximized state, but it doesn't properly restore
those maximized windows to their previous dimensions.

Comment 5

[Ari Pollak]

Thanks to John for pointing out where the setting is saved, it is a much better
solution (until I maximize a window again) for me than to use the window manager
settings.

Comment 6

[John Wright]

It looks like this bug is fixed as of Mozilla 1.4a.

Comment 7

[John Wright]

Oops - looks like it's actually reverting to the previous method that doesn't
save maximization state, only window size and position.  So if you close a
maximized window, next time you open that type of window, it will be maximized
in size, but it will have no way to un-maximize it - it starts in a 'restored'
state.

I'm sure there's another bug for this (seems like it's been open for a long
time, and perhaps the behavior in 1.3 was an attempted fix for it), but it's
late and I think I'll go to bed rather than bother finding it...

Actually, I think the bug I'm thinking of is the one the reporter mentioned (bug
32148).  In any case, its current (1.4a) behavior is less annoying than that of
1.3, as long as you remember to restore the window state before closing it...

Comment 8

[Ari Pollak]

It looks like this is all part of one massive Debian
purge-the-package-and-all-the-bugs-will-go-away bug, focused by Debian bugs
181030, 185302, 185935, 186046, 186339, 187706, and 187719.

Comment 9

[Ari Pollak]

Oh wait no, sorry.. Looks like this is seperate.

Comment 10

[Richard Trout]

I confirm this bug in Windows 2000. 

Comment 11

[Ari Pollak]

Thanks. marking all platforms.

Comment 12

[Dan M]

I see no problem on any platform but *nix. My Win2k, WinXP and OSX boxes are all
behaving well. But I'm having trouble in RedHat 8 with the Metacity WM. I
suspect it's Metacity's fault, or I should say some interaction between Metacity
and Mozilla that's new with Metacity. Is everyone who sees this problem, by any
chance, using a recently updated Window Manager? Richard, you and your Win2k,
obviously not, but again, I don't see this problem on Win2k. (Do you perhaps
have a corrupt localstore.rdf file? (See bug 96221 comment 13, bug 88563 comment
15, and bug 99235, where the last *known* cause of that was fixed.))

The reason it seems like a WM interaction problem is that we make no attempt to
save maximized state on *nix platforms. (Using gtk! We do address the issue if
you've built Mozilla using gtk2 (see bug 121259), but I'm very unsure exactly
how well that works. My last knowledge on this subject comes from bug 32148
comment 108 (damn, this comment is a hyperlink festival). That's still true at
least in gtk, which is what I'm running.

Last paragraph restated: on *nix builds (running gtk, as I am) we aren't even
notified when a window is maximized. sizemode is never "maximized" in
localstore.rdf. Despite that, maximize the window, quit Mozilla and restart, and
the first window is opened maximized. I never saw this before installing
Metacity and it's gotta be something it's doing. I bet Chris knows. I'd like to.

Comment 13

[Christopher Blizzard (:blizzard)]

I fixed this a while ago.

*** This bug has been marked as a duplicate of 198284 ***