Repository navigation
bd352f1
Pre-release
Pre-release
fix(wm): Keep a size for windows maximized or fullscreen before they map
A window that changed its decoration while maximized kept the client
area of the frame it had, so a toplevel maximized as it opened and then
asking to draw its own frame was configured short of its work area. A
decoration change now fits the window's state again.
A client's maximize before its first commit was dropped, and a
fullscreen before it saved the empty placeholder as the geometry to
return to, so leaving it configured the window at 0x0. A window that
opened maximized at a geometry of its own, as an X11 client maps one,
did not save that geometry and restored to two thirds of its work area.
- Only a geometry with a size is saved to return to; a window opening
maximized or fullscreen at a requested size saves it. - A maximize is taken before the window maps.
- Leaving either state goes through one restore: the saved geometry,
else, before the window maps, back to no size so the client chooses
one and the window is placed on map, else the first restore frame,
which a fullscreen without a saved geometry now takes as well.