Bug 98585

Summary:	Xquartz 2.7.11, maximize windows doesn't work on secondary display
Product:	XQuartz	Reporter:	Mao <peterm>
Component:	quartz-wm	Assignee:	Jeremy Huddleston Sequoia <jeremyhu>
Status:	RESOLVED MOVED	QA Contact:	Jeremy Huddleston Sequoia <jeremyhu>
Severity:	normal
Priority:	medium	CC:	peterm
Version:	2.7.10 (xserver-1.18.4)
Hardware:	Other
OS:	Mac OS X (All)
Whiteboard:
i915 platform:		i915 features:

Description Mao 2016-11-04 00:57:12 UTC

When the laptop display has the toolbar, the window snaps back to the primary display, even though the window started in the secondary display.  When the toolbar is in the secondary display, maximizing the window changes it to the size of the laptop display, but keeps the window in the larger secondary display.

This was working properly in 2.7.7.  The desired behavior is for the window to maximize in the display in which it resides.

I'm running OS X Sierra on a MacBook Pro (intel i7 2.9 GHz processor) with an external monitor attached.

Comment 1 Jeremy Huddleston Sequoia 2016-11-04 05:11:29 UTC

Can you please bisect to figure out what version introduced the issue for you?

Comment 2 Mao 2016-11-08 18:20:05 UTC

The problem begins with 2.7.11.  I installed 2.7.10, and the green button behavior is normal.

Comment 3 Jeremy Huddleston Sequoia 2016-11-09 01:15:39 UTC

There was literally no change between 2.7.10 and 2.7.11 in that code.

The only changes were 4 small patches for very targeted issues (in fontcnonfig, libX11, and libXi) and version bumps for libpng and mesa.

Comment 4 GitLab Migration User 2019-05-23 18:18:20 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/app/quartz-wm/issues/4.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.