https://bugs.winehq.org/show_bug.cgi?id=50381
Rémi Bernon rbernon@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rbernon@codeweavers.com
--- Comment #9 from Rémi Bernon rbernon@codeweavers.com --- The problem here is that MATE WM (https://github.com/mate-desktop/marco) restores some saved window position whenever the client requests a window to be "unmaximized" by changing _NET_WM_STATE. The saved position is only updated whenever the window gets maximized.
With the _NET_WM_STATE updates being sent even when no change is actually done, marco restores the position to its saved position every time we update the state. This makes the window jump to its original position (where it was initially created or where it was on the last maximization). Then we usually move the window position too, and this makes it jump back to where it's now supposed to be, and again.
We could on our side avoid requesting the maximize state change when it's not necessary but I think this is also a bug in marco, as it should either not unmaximize the window again if it's already unmaximized, or update its saved position after the window got unmaximized, as well as when the window is moved.