[PATCH wayland v2 1/2] protocol: Clarify semantics of sub-surface placement requests

[Jonas Ådahl]

Clarify some semantics of wl_subsurface.place_below and
wl_subsurface.place_below that were not specified.

Signed-off-by: Jonas Ådahl <jadahl at gmail.com>
---

Hi,

Hope this one makes more sense. In this version I changed the original
double-buffer description instead of adding a new paragraph.


Jonas

 protocol/wayland.xml | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/protocol/wayland.xml b/protocol/wayland.xml
index 61fde84..b986c86 100644
--- a/protocol/wayland.xml
+++ b/protocol/wayland.xml
@@ -1946,8 +1946,9 @@
 	parent surface. Using any other surface, including this sub-surface,
 	will cause a protocol error.
 
-	The z-order is double-buffered state, and will be applied on the
-	next commit of the parent surface.
+	The z-order is double-buffered. Requests are handled in order and
+	applied immediately to a pending state, then committed to the active
+	state on the next commit of the parent surface.
 	See wl_surface.commit and wl_subcompositor.get_subsurface.
 
 	A new sub-surface is initially added as the top-most in the stack
-- 
1.8.3.2