[PATCH wayland-protocols v3 16/17] xdg-shell: Clarify set_fullscreen semantics
jadahl at gmail.com
Wed Nov 15 11:20:05 UTC 2017
It was not explicitly specified (as it is in set/unset_maximize) that
the compositor will respond with a configure event when a client asks to
be fullscreened, and the meaning of the output parameter was somewhat
Signed-off-by: Jonas Ådahl <jadahl at gmail.com>
Reviewed-by: Mike Blumenkrantz <zmike at samsung.com>
stable/xdg-shell/xdg-shell.xml | 13 ++++++++++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/stable/xdg-shell/xdg-shell.xml b/stable/xdg-shell/xdg-shell.xml
index 6101413..8c7efab 100644
@@ -886,9 +886,16 @@
<description summary="set the window as fullscreen on an output">
Make the surface fullscreen.
- You can specify an output that you would prefer to be fullscreen.
- If this value is NULL, it's up to the compositor to choose which
- display will be used to map this surface.
+ After requesting that the surface should be fullscreened, the
+ compositor will respond by emitting a configure event with the
+ "fullscreen" state and the required window geometry. The client must
+ also acknowledge the configure when committing the new content (see
+ The output passed by the request indicates the client's preference as
+ to which display it should be set fullscreen on. If this value is NULL,
+ it's up to the compositor to choose which display will be used to map
+ this surface.
If the surface doesn't cover the whole output, the compositor will
position the surface in the center of the output and compensate with
More information about the wayland-devel