diff options
| author | Zhiyi Zhang <[email protected]> | 2021-04-14 16:03:31 +0800 |
|---|---|---|
| committer | Victor Kareh <[email protected]> | 2021-04-30 09:47:57 -0400 |
| commit | 60f49ae5a272b737a944065e4199c8b2c8eec8b1 (patch) | |
| tree | c96d873e387d760158358adfe624f87fd35482b8 /po/ku_IQ.po | |
| parent | aebd99901c99c49944bc514020f4517c545111c7 (diff) | |
| download | marco-60f49ae5a272b737a944065e4199c8b2c8eec8b1.tar.bz2 marco-60f49ae5a272b737a944065e4199c8b2c8eec8b1.tar.xz | |
window: Only unmaximize when the window is already maximized.
When handling a ClientMessage event that removes _NET_WM_STATE_MAXIMIZED_HORZ
or _NET_WM_STATE_MAXIMIZED_VERT from _NET_WM_STATE, marco always restore the
window rectangle to the saved rectangle. So if an application window is already
unmaximized and the application sends such a ClientMessage event, marco will
reset the window rectangle regardless. EWMH doesn't specify what must be done
when handling such events. It seems best to avoid restoring window rectangles
like other window managers in this case.
Fix a related bug: https://bugs.winehq.org/show_bug.cgi?id=50381
This revert a change introduced by 6219f8e8bcaeefb9185a3c3f5f20de4e2fa8f18f.
Signed-off-by: Zhiyi Zhang <[email protected]>
Diffstat (limited to 'po/ku_IQ.po')
0 files changed, 0 insertions, 0 deletions