https://bugs.kde.org/show_bug.cgi?id=441074

--- Comment #16 from redartofc...@gmail.com ---
(In reply to Vlad Zahorodnii from comment #12)
> As David said, this is an intentional behavior.
> 
> Also, yes, the stacking order in the NETWM spec is a recommendation but the
> applications are written with that recommended stacking order in mind. So if
> we start changing that, we can break more things than we try to fix.

I understand. As a workaround, I just added the no titlebar / frame rule to the
game and set its size to almost full monitor resolution. That makes everything
work well.

I am confused about windowed fullscreen vs fullscreen at this point. It seems
both of them are the same from the perspective of KDE? Fullscreen just adds the
additional behavior that if the game lost focus, it minimizes itself. 

Anyway, there's also a another related bug at
https://bugs.kde.org/show_bug.cgi?id=442720 regarding cursor staying grabbed by
the game even if I try to click on the windows above it (firefox PiP player or
notifications). I set the layer for the game "below" to make sure the others
stay above. Notifications seem to go below the windowed fullscreen game (That
behavior seems new. In the past, notifications still appeared above, even if
non-clickable due to mouse grab).

I am not even sure if that is a bug or just intended behavior. So, please
review that too if you have some time :)

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to