We currently don't have a consistent idea and behaviour as to what should happen if the remote session resizes when the client window is maximized. Right now the defined behaviour is: * If fullscreen, keep local window size at all times (i.e. stay in fullscreen) * If the session size currently perfectly matches the window size, then follow changes to the session size to keep them in sync * Otherwise keep the local window size This fails to handle the fact that the local window manager tends to want to preserve the maximized state of a window. Perhaps a strategy similar to what we do for fullscreen is approriate. Observed behaviour right now is: * Windows: Window resizes if smaller, but window decorations suggest that the window manager still thinks the window is maximized. * Linux (GNOME): The window manager allows the resize, then immediately restores the maximized size. This counts as a local resize and triggers a request to resize the server session, effectively undoing the resize from the server to the client. * macOS: Not tested.
This might have got fixed as a side effect of resolving bug 7265. Need to test.
Tested this again using client 3801. Windows 11, Fedora 40 GNOME, macOS 15: * If fullscreen, keep local window size at all times (i.e. stay in fullscreen) - Leaving fullscreen will make the window resize to the size it had before entering fullscreen. * If the session size currently perfectly matches the window size, then follow changes to the session size to keep them in sync. * Otherwise, (when maximized), keep the local window size. Closing as this seems to have been fixed some time ago (bug 7265?).
