LGUG2Z
e563988258
A fullscreen window covers its monitor on purpose. Moving it would take it out of fullscreen, or be ignored, so Window::set_position does nothing for a fullscreen window, and every move the window manager makes goes through it. The bridge reports KWin's fullScreenChanged as a fullscreen event, and the table keeps what it says, which is what the window manager asks. The window stays in its container, and the others are tiled as if it were not fullscreen. When it comes back from fullscreen, KWin gives it the frame it had before, which may not be its tile any more, so the workspace is tiled again. Section E of the features suite checks it in a real Plasma session: a fullscreen window covers the monitor, a window that opens does not take it out of fullscreen, and it is in a tile that overlaps no other when it comes back.
998 B
Fullscreen windows
A window that goes fullscreen, with its program's own key (F11 in many programs), the window menu or a shortcut, covers its whole monitor, the panels included. komorebi leaves it there. It never moves or resizes a fullscreen window, whatever happens to the others: a retile, a window that opens or closes, a layout that changes.
The window stays in its container, so the layout keeps a tile for it, and the other windows are tiled as if it were not fullscreen. The fullscreen window covers them, and they are in their tiles when it leaves.
When the window leaves fullscreen, KWin gives it the frame it had before. That frame may not be its tile any more, because windows can have opened or closed meanwhile, so komorebi tiles the workspace again and the window goes to the tile the layout has for it.
There is no komorebic command for fullscreen: it is KWin's, and the program's. A window that is
fullscreen when komorebi starts is left alone the same way.