Description:
Assuming 2 workspaces on 2 monitors. If workspace 2 has a fullscreen application, trying to move any application from workspace 1 to workspace 2 will yield some weird behavior. In theory, application has moved to workspace 2, since it can no longer be interacted with in workspace 1, but its surface is still rendered on workspace 1. This is fixed by either hiding workspace 2 (changing monitor 2 to workspace 3) or by removing fullscreen mode from the application on workspace 2.
Tried with EGL rendered as well just to confirm it wasn't Vulkan related. Also tried with sway 1.10 stable, same behavior.
Example 1
Moved alacritty to workspace that contains a fullscreen application. Second application (zen browser) acts like alacritty is no longer in the workspace, but alacritty is still being rendered.
Example 2
Zen browser is moved, alacritty acts like zen browser is no longer there, but zen browser is still being rendered.
Sway Version: 1.10-dev-d417a8fc
Debug Log: sway log
Description: Assuming 2 workspaces on 2 monitors. If workspace 2 has a fullscreen application, trying to move any application from workspace 1 to workspace 2 will yield some weird behavior. In theory, application has moved to workspace 2, since it can no longer be interacted with in workspace 1, but its surface is still rendered on workspace 1. This is fixed by either hiding workspace 2 (changing monitor 2 to workspace 3) or by removing fullscreen mode from the application on workspace 2.
Tried with EGL rendered as well just to confirm it wasn't Vulkan related. Also tried with sway 1.10 stable, same behavior.
Moved alacritty to workspace that contains a fullscreen application. Second application (zen browser) acts like alacritty is no longer in the workspace, but alacritty is still being rendered.
Zen browser is moved, alacritty acts like zen browser is no longer there, but zen browser is still being rendered.