On Thu Feb 19 17:13:56 2026 +0000, Rémi Bernon wrote:
I see. Well it seems that other WMs only offer activation *after* sending the WM_STATE update, which kind of makes sense IMO: no good reason for clients that aren't aware of a window being mapped to expect it to be activated either. I'm not completely sure how to fix it, it's a very brittle assembly and changes are often causing more issues than they fix. What's exactly wrong with this patch's fix though? If we skip the activation (which is fine), shouldn't we later activate it if needed?
I just fail to see a justification for the pending_state's net_active_window to be set to a window which we did not explicitly sent _NET_ACTIVE_WINDOW to. Can you give an example sequence where the current logic is good and this patch fails? -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10133#note_129979