inconsistent maximise and fullscreen behaviour for fixed-sized Wayland clients
Affected version
mutter master, Wayland
Bug summary
Wayland clients that set a fixed size by setting equal minimum (set_min_size
) and maximum (set_max_size
) limits do behave differently when they are maximised (set_maximized
) or set to fullscreen (set_fullscreen
).
While a maximise request is inhibited, a fullscreen request is followed through with the client keeping its size but the shell appearing as if the client is in fullscreen mode.
Steps to reproduce
- compile the libdecor demo
- start
libdecor-demo
- press the following key combination:
-
1
to set non-resizeable -
2
and3
to maximise and unmaximise again -> nothing is happening, client does not change state -
4
and5
to set and unset fullscreen mode -> shell assumes fullscreen client but toplevel size stays the same
-
What happened
The non-resizeable client behaves differently when requesting maximise and fullscreen mode.
What did you expect to happen
The client should be configured with the maximised and fullscreen dimension respectively, and decide itself how to proceed (i.e. accept configuration or decline it).
Relevant logs, screenshots, screencasts etc.
Inconsistent state in fullscreen mode:
Edited by Christian Rauch