After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 581982 - Double clicking a maximized window frame does not restore window
Double clicking a maximized window frame does not restore window
Status: RESOLVED OBSOLETE
Product: metacity
Classification: Other
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2009-05-09 12:52 UTC by lordmetroid
Modified: 2020-11-06 20:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description lordmetroid 2009-05-09 12:52:11 UTC
Please describe the problem:
Normally a double click on a window's titlebar the window should restore from maximized to user set size. This works in normal cases however when an application starts maximized and the user tries to performs this procedure in order to restore the window size(expecting a smaller window only covering part of the screen). The window flickers and for a brief moment as I assume it obtains the previous user set size but then goes back to cover the whole screen but not in maximized mode.

Steps to reproduce:
1. Start firefox(mine starts in maximized mode, other applications does not)
2. Double click on titlebar

Actual results:
Window flicker and you get a window frame that is in non-maximized mode covering the whole screen

Expected results:
The window frame to become smaller

Does this happen every time?
Yes

Other information:
Comment 1 lordmetroid 2009-05-09 13:22:46 UTC
Using Ubuntu 9.04
Linux lordmetroid-stationary 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux
Comment 2 André Klapper 2020-11-06 20:06:41 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/metacity/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.