On Mon Aug 11 07:49:35 2025 +0000, Rémi Bernon wrote:
I'm still wondering whether this is the right thing to do. Maybe we're wrong telling the driver and the host that a window is fullscreen as soon as it entirely covers one of the monitors. On a multi-monitor system, if a window covers one monitor and part of another, it probably shouldn't be using _NET_WM_STATE_FULLSCREEN as that would reduce it to only the monitor it covers right?
Yeah, I had an old patch that doesn't mark the window as fullscreen if the window rect doesn't match the monitor rect exactly, see https://gitlab.winehq.org/zhiyi/wine/-/commit/d236213b, but I didn't get it upstream at the time due to some potential problems. For example, I remember some games use a slightly larger window rect. Not having _NET_WM_STATE_FULLSCREEN will cause the taskbar to be shown on top of the game window. I will revisit d236213b and compare with native and see if a similar fix can be used.