Consolatis

> Your original code, is probably fine, but rather than put the modified desktop_cycle* in desktop.c I think it fits better being added to the regions.c code as it really...

Just to mention, the Void-musl runtime tests fails because `output_frame_notify()` is triggered before the session is initialized (`server->session` still at `NULL`). This might happen when labwc runs with headless outputs...

Just asked in the wlroots channel regarding the unreliable `session->active` state and it turns out on affected versions of libseat this may be `true` instead of `false`. So on these...

Just for completeness, you can also use the mouse to snap a window to a region by pressing any keyboard modifier after the move has started.

Theoretical options to allow for this use-case: - some argument for the `UnMaximize` action - some new action like `SetFloating`

Personally I also prefer to not accidentally store a bunch of 8k images in various formats including BMP in compositor memory (or whatever else some random application puts into the...

> It would be nice if we could keep the original offer intact, and only replace it with a fallback if the application actually quits. The fallback could be restricted...

> Using `wlr-data-control-unstable-v1` for this purpose is racey; when the clipboard is taken multiple times in quick succession, the clipboard manager has no way to assert whether the clipboard was...

> What the 'fullscreen' option should do is a matter of preference. The idea from #1568 where 'fullscreen' ignores the tearing hint, is still valid and may be this option...

> Another thing regarding tearing is that we should do something different than checking WLR_DRM_NO_ATOMIC to find if tearing is supported. Its already merged in the master branch: - #1996