summaryrefslogtreecommitdiff
path: root/stable
diff options
context:
space:
mode:
authorSimon Ser <contact@emersion.fr>2020-04-07 17:28:54 +0200
committerSimon Ser <contact@emersion.fr>2020-04-07 17:50:45 +0200
commit684cd23ae31fafb9eda2a0cd15edb4e96de92259 (patch)
tree4e07338c9e3a977dae8d3db0de933e7ab8ded04f /stable
parente8f7d4ebbd3d85b174e965ad601d806a49238696 (diff)
xdg-shell: explain how clients need to perform an initial commit
This wasn't explicit reading the mapping requirements. Signed-off-by: Simon Ser <contact@emersion.fr>
Diffstat (limited to 'stable')
-rw-r--r--stable/xdg-shell/xdg-shell.xml5
1 files changed, 5 insertions, 0 deletions
diff --git a/stable/xdg-shell/xdg-shell.xml b/stable/xdg-shell/xdg-shell.xml
index b77eee1..f7377a7 100644
--- a/stable/xdg-shell/xdg-shell.xml
+++ b/stable/xdg-shell/xdg-shell.xml
@@ -426,6 +426,11 @@
manipulate a buffer prior to the first xdg_surface.configure call must
also be treated as errors.
+ After creating a role-specific object and setting it up, the client must
+ perform an initial commit without any buffer attached. The compositor
+ will reply with an xdg_surface.configure event. The client must
+ acknowledge it and is then allowed to attach a buffer to map the surface.
+
Mapping an xdg_surface-based role surface is defined as making it
possible for the surface to be shown by the compositor. Note that
a mapped surface is not guaranteed to be visible once it is mapped.