On Fri Apr 17 12:51:31 2026 +0000, Zhiyi Zhang wrote:
but as I said above I don't think it should matter from our perspective, it's rather something the WM should worry about? According to [_NET_WM_FULLSCREEN_MONITORS](https://specifications.freedesktop.org/wm/latest/ar01s06.html), "In the event of a change in monitor configuration, the application is responsible for re-computing the monitors on which it wants to appear. The window manager may continue using the same monitor indices as before or simply clear the list, returning to "normal" fullscreen." It's our responsibility to set and update _NET_WM_FULLSCREEN_MONITORS accordingly. I think that in the case it "continue using the same monitor indices" and if the monitor indices don't change, then it wouldn't make a difference if we request them again or not. If the WM wants us to actually provide updated indices, it would be the "clear the list" case, which we could handle by tracking property deletions.
But in any case, I think this scenario is just completely racy already right now and regardless of whether indices match or not: the sequence between monitor layout updates from XRandR, sysparams monitor updates, window repositioning on the corresponding WM_DISPLAYCHANGE, and corresponding WindowPosChanged calls, is very much undefined and unlikely to give deterministic results. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10620#note_136742