Firefox forgets unmaximised size when closed

[Ian Redfern]

Binary package hint: firefox

Open a single Firefox window, unmaximised, taking up only part of the screen. Maximise it. Quit Firefox. Start Firefox.

You will have a single maximised window, as expected. But if you unmaximise the window, it stays at maximised size and doesn't return to the original size.

This is annoying if you have your Firefox window at a preferred size - you have to remember to unmaximise before quitting.

Found in both Feisty and Gutsy - firefox_2.0.0.4+2-0ubuntu1_i386.deb

[Hilario J. Montoliu (hjmf) (hmontoliu)]

Thank you Ian Redfern for your report,

I cannot reproduce your issue in feisty. Here it behaves as expected, the unmaximized size is kept when I try to reproduce your testcase (unmaximize, resize, maximize, close, open, unmaximize).

This is using Metacity + Gnome. Which is your environment?

Thank you in advance.

[Ian Redfern (ian-redfern)]

Ah, this only happens under Beryl, not Metacity. I've just tried it with gedit, and it shows the same problem under Beryl, so it's nothing to do with Firefox.

Looks like this is a Beryl bug - my apologies.

[VLK (valentyn)]

This problem occurs not only to Firefox but to any window in Feisty (e.g. Nautilus, Opera, etc.). I'm using standard Human theme (metacity), and it annoys me a very long time already!

Steps to reproduce:

1. open Home Folder (Places -> Home Folder). It opens in a UNMAXIMIZED window, which is 1/4 of my whole screen.
2. maximize the window by pressing MAXIMIZE button (or just press Alt+F10).
3. close the window
4. open Home Folder again. The window opens MAXIMIZED.
5. press UNMAXIMIZE button (or press Alt+F5).
6. the window becomes UNMAXIMIZED, but remains in the full screen, so you have to resize it (again and again...) manually.

Suggestion:

The windows manager has to remember the value of UNMAXIMIZED window even if it was MAXIMIZED.

[VLK (valentyn)]

I think this bug report is similar to Bug #137479. It should be triaged.

[positivek (anonyhole)]

Why not change the bug subject since it was mentioned that this does not have to do with Firefox?

[Alexander Sack (asac)]

On Fri, Jan 04, 2008 at 05:53:28PM -0000, positivek wrote:
> Why not change the bug subject since it was mentioned that this does not
> have to do with Firefox?
>

i think firefox could fix this at some point.

 affects ubuntu/firefox-3.0
 status confirmed

firefox 2 won't receive any fix anymore though

 affects ubuntu/firefox
 status wontfix

 - Alexander

[Ian Redfern (ian-redfern)]

I can confirm that the original bug was in Beryl, not Firefox, and was fixed in Gutsy by Compiz. Please close it - it has nothing to do with Firefox.

Thanks,
Ian Redfern

[Alexander Sack (asac)]

On Tue, Jan 08, 2008 at 10:57:59PM -0000, Ian Redfern wrote:
> I can confirm that the original bug was in Beryl, not Firefox, and was
> fixed in Gutsy by Compiz. Please close it - it has nothing to do with
> Firefox.
>

Thanks for the info.

 affects ubuntu/firefox-3.0
 status invalid

 - Alexander