From e71ed40ad7afb68d22c1ebbc38ad5cc80fa0e12f Mon Sep 17 00:00:00 2001
From: Xaver Hugl <xaver.hugl@gmail.com>
Date: Wed, 17 Apr 2024 18:37:27 +0200
Subject: [PATCH] staging/tearing-control: clarify what happens after
wl_surface destruction
There's no protocol error for making requests on the object after the wl_surface
has been destroyed, so the object has to become inert in that case.
Signed-off-by: Xaver Hugl <xaver.hugl@kde.org>
---
staging/tearing-control/tearing-control-v1.xml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/staging/tearing-control/tearing-control-v1.xml b/staging/tearing-control/tearing-control-v1.xml
index 0d4dc678..9c44fbfc 100644
--- a/staging/tearing-control/tearing-control-v1.xml
+++ b/staging/tearing-control/tearing-control-v1.xml
@@ -75,6 +75,9 @@
presentation with tearing.
The default presentation hint is vsync. See presentation_hint for more
details.
+
+ If the associated wl_surface is destroyed, this object becomes inert and
+ should be destroyed.
</description>
<enum name="presentation_hint">
--
GitLab