<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - wayland: new window momentarily displays on wrong monitor" href="https://bugzilla.gnome.org/show_bug.cgi?id=782183#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - wayland: new window momentarily displays on wrong monitor" href="https://bugzilla.gnome.org/show_bug.cgi?id=782183">bug 782183</a> from <a href="page.cgi?id=describeuser.html&login=ofourdan%40redhat.com" title="Olivier Fourdan <ofourdan@redhat.com>"> Olivier Fourdan</a> <pre>For the size, sure the client is in charge, but the location still needs to be set/restored, and placement depends on the size. BTW, I think there is more to it than just maximize_*_after_placement, if you remove that from meta_window_maximize() (as a test), the initial map animation still shows on the first monitor when the window is maximized on the second monitor (which is this bug. different from <a class="bz_bug_link bz_status_NEW " title="NEW - wayland: presenting maximized window is jittery" href="show_bug.cgi?id=781353">bug 781353</a> even if related) To reproduce: 1. MUTTER_DEBUG_NUM_DUMMY_MONITORS=2 jhbuild run mutter --wayland --nested 2. Place the mouse pointer on the (fake) screen on the right 3. Launch an application that starts maximized (e.g. totem if closed while maximized) => The inital map animation plays on the monitor on the left and the window eventually shows on the monitor on the right (where the pointer is located, as this makes the "current" monitor)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>