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 419810 - New windows that are created at max height are stuck on the top/bottom edges
New windows that are created at max height are stuck on the top/bottom edges
Status: VERIFIED FIXED
Product: metacity
Classification: Other
Component: general
trunk
Other Linux
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
: 430007 447205 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-03-18 17:48 UTC by Kalle Vahlman
Modified: 2007-06-14 00:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18

Attachments
Patch that should fix this (970 bytes, patch)
2007-04-12 22:27 UTC, Elijah Newren 		committed Details | Review

Description Kalle Vahlman 2007-03-18 17:48:21 UTC 
Setup:

Single 24px gnome-panel at the top of the screen

Steps:

1. Open a window placement remembering app (like epiphany)
2. Resize it so that it takes maximum space available vertically
3. Close the app
4. Open the app

Expected:

You can drag and resize the window vertically

Actual result:

The window sticks to the top and bottom of the area like a handful of wonderglue
The only way to shake it off seems to be to maximize it and then drag it off from that state. Even ALT-drag doesn't work.
Comment 1 Elijah Newren 2007-03-18 19:59:33 UTC 
Hmm, I guess auto vertical/horizontal maximization isn't such a great idea when only one of the two is relevant (especially since we only have UI feedback for fully maximized windows and horziontal/vertical maximization keybindings aren't bound by default).  See metacity/src/place.c:meta_window_place(), search for maximize_(horizontally|vertically)_after_placement.
Comment 2 Elijah Newren 2007-04-12 22:27:30 UTC 
Created attachment 86271 [details] [review]
Patch that should fix this
Comment 3 Kalle Vahlman 2007-04-13 07:05:05 UTC 
And so it is! Nice.

(verifying)
Comment 4 Elijah Newren 2007-04-15 18:26:27 UTC 
*** Bug 430007 has been marked as a duplicate of this bug. ***
Comment 5 Elijah Newren 2007-06-14 00:11:23 UTC 
*** Bug 447205 has been marked as a duplicate of this bug. ***