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 321902 - New maximized windows have an extra border
New maximized windows have an extra border
Status: RESOLVED FIXED
Product: metacity
Classification: Other
Component: general
2.13.x
Other Linux
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
: 322061 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-11-20 03:17 UTC by Josh Lee
Modified: 2005-11-21 18:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Attachments
Screenshot showing the mysterious border (43.08 KB, image/png)
2005-11-20 03:18 UTC, Josh Lee
  Details
Compute the frame geometry due to maximization after actually maximizing (1.25 KB, patch)
2005-11-20 21:56 UTC, Elijah Newren
committed Details | Review

Description Josh Lee 2005-11-20 03:17:40 UTC
I just downloaded metacity 2.13.2 and found the following bug:

When opening a new maximized window, it has an extra border on the right. The 
entire window, including the titlebar, is several pixels narrower on the sides 
and bottom. The width of the border is equal to the width of an unmaximized 
border for that side. The border goes away once the window is unmaximized.

This bug is probably some kind of weird interaction with the new constraints 
code.
Comment 1 Josh Lee 2005-11-20 03:18:09 UTC
Created attachment 54956 [details]
Screenshot showing the mysterious border
Comment 2 Elijah Newren 2005-11-20 03:43:13 UTC
Unfortunately, I can't duplicate.  Does this happen for you with other themes? 
Does it occur only when the window is initially placed and happens to be
maximized?  Does it happen for all windows that you maximize or only certain ones?
Comment 3 Josh Lee 2005-11-20 17:29:50 UTC
This happens with other themes, too. It only happens for initially maximized 
windows, but it happens all the time.

More information:
Metacity seems to think that the window is not maximized. Using the "Unmaximize" 
command does nothing on the window, but using the "Maximize" command causes the 
extra borders to go away. Next, when the window is unmaximized, it is the size 
of all the available space, instead of smaller like it should be.

You probably shouldn't worry too hard about this bug. I've been trying out 
debian experimental recently, so there might be a funny library thing going on. 
See if anyone else encounters it.

(Close as INVALID, maybe)
Comment 4 Elijah Newren 2005-11-20 17:57:26 UTC
Oops, I accidentally reversed the order of the meta_window_maximize_internal()
and meta_frame_calc_geometry() calls in the constraints code (now in
place_window_if_needed(); the same code used to be inside
meta_window_constrain()).  Thanks for the initially maximized hint.  I gotta run
now but I'll post a patch later to fix this up...
Comment 5 Elijah Newren 2005-11-20 21:56:01 UTC
Created attachment 54993 [details] [review]
Compute the frame geometry due to maximization after actually maximizing

Could you check and verify that this patch fixes the problem for you?  Thanks.
Comment 6 Josh Lee 2005-11-21 01:53:19 UTC
Yes! This works! Thanks a bunch, Elijah.
Comment 7 Elijah Newren 2005-11-21 06:00:28 UTC
Committed then, as the patch is simple enough.

2005-11-20  Elijah Newren  <newren@gmail.com>

	* src/constraints.c (place_window_if_needed): compute the frame
	geometry due to maximization only after actually maximizing.
	Fixes #321902.
Comment 8 Elijah Newren 2005-11-21 18:49:41 UTC
*** Bug 322061 has been marked as a duplicate of this bug. ***