summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKirill Primak <vyivel@eclair.cafe>2022-10-15 20:05:34 +0300
committerSimon Ser <contact@emersion.fr>2022-11-29 13:46:54 +0000
commit68dfa1183f937a9a34d0a8582e4ffe5eace4a32d (patch)
tree9e56a2b5b4184f4e26f33a2c314b4b7babf49dab
parent86d73b2da221bc9ca059195af4c97297fd5221c6 (diff)
downloadwayland-68dfa1183f937a9a34d0a8582e4ffe5eace4a32d.tar.gz
protocol: remove wl_subsurface lifetime contradiction
This statement assumes that a wl_surface can be destroyed before the corresponding wl_subsurface, which is not true, as wl_surface description explicitly states that the role object must be destroyed before the wl_surface itself. Signed-off-by: Kirill Primak <vyivel@eclair.cafe>
-rw-r--r--protocol/wayland.xml10
1 files changed, 4 insertions, 6 deletions
diff --git a/protocol/wayland.xml b/protocol/wayland.xml
index 99732c5..6589d5e 100644
--- a/protocol/wayland.xml
+++ b/protocol/wayland.xml
@@ -2938,12 +2938,10 @@
synchronized mode, and then assume that all its child and grand-child
sub-surfaces are synchronized, too, without explicitly setting them.
- If the wl_surface associated with the wl_subsurface is destroyed, the
- wl_subsurface object becomes inert. Note, that destroying either object
- takes effect immediately. If you need to synchronize the removal
- of a sub-surface to the parent surface update, unmap the sub-surface
- first by attaching a NULL wl_buffer, update parent, and then destroy
- the sub-surface.
+ Destroying a sub-surface takes effect immediately. If you need to
+ synchronize the removal of a sub-surface to the parent surface update,
+ unmap the sub-surface first by attaching a NULL wl_buffer, update parent,
+ and then destroy the sub-surface.
If the parent wl_surface object is destroyed, the sub-surface is
unmapped.