<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#c15">Comment # 15</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=jadahl%40gmail.com" title="Jonas Ådahl <jadahl@gmail.com>"> Jonas Ådahl</a> <pre>(In reply to Olivier Fourdan from <a href="show_bug.cgi?id=782183#c14">comment #14</a>) > I think there is another thing to consider, if we remove the > "maximize_*_after_placement" logic, the windows will most likely be > misplaced when eventually they're de-maximized (as maximization is supposed > to save the previous size/position so that de-maximizing a window restores > the previous pre-maximization location and size on screen). AFAICS, with force_place() before maximize() will end up not setting any old rect. I think that also actually makes sense. We should probably not have mutter pretend to know what to restore to, as in Wayland that is up to the client. Initially we send 0x0, and I guess when restoring to something unknonw, we should send 0x0 too.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>