<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Wayland: not fullscreenable gtk+ apps can be fullscreened" href="https://bugzilla.gnome.org/show_bug.cgi?id=764413#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Wayland: not fullscreenable gtk+ apps can be fullscreened" href="https://bugzilla.gnome.org/show_bug.cgi?id=764413">bug 764413</a> from <a href="page.cgi?id=describeuser.html&login=ofourdan%40redhat.com" title="Olivier Fourdan <ofourdan@redhat.com>"> Olivier Fourdan</a> <pre>Ah right, here it is... It was <a href="attachment.cgi?id=314814&action=diff" name="attach_314814" title="[Patch 2/3] wayland: apply maximized state only when possible">attachment 314814</a> <a href="attachment.cgi?id=314814&action=edit" title="[Patch 2/3] wayland: apply maximized state only when possible">[details]</a> <a href='review?bug=764413&attachment=314814'>[review]</a> in <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - GtkWindow reacts on maximize action even if it is fixed-width" href="show_bug.cgi?id=757530">bug 757530</a> - It needs a rebase most likely as this code has changed since then, and probably some work as well, but the idea is that in Wayland, the compositor doesn't have any hint what the size limit a window may have as this is handled entirely by the client, so the compositor cannot tell whther or not a window can be maximized/fullscreened beforehand... So the client (ie gtk+ in this case) has to adjust its state if it doesn't match. Or else you'll need an xdg-shell addition to give the compositor a hint, but this was not accepted in the past (Was just dicussing this with Jasper yesterday on irc...)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>