From 7c6a510a602be7747c857660ef148f9f5c10fd5c Mon Sep 17 00:00:00 2001 From: Xaver Hugl Date: Fri, 12 Apr 2024 17:05:18 +0200 Subject: [PATCH] staging/alpha-modifier: relax the rules around surface destruction When the client crashes, the compositor has to be able to cope with any order of object destruction, so there is no practical reason to enforce the surface extension to be destroyed before the surface itself. Signed-off-by: Xaver Hugl --- staging/alpha-modifier/alpha-modifier-v1.xml | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/staging/alpha-modifier/alpha-modifier-v1.xml b/staging/alpha-modifier/alpha-modifier-v1.xml index 932fa6f..cda1bfc 100644 --- a/staging/alpha-modifier/alpha-modifier-v1.xml +++ b/staging/alpha-modifier/alpha-modifier-v1.xml @@ -64,9 +64,8 @@ a surface, which can be used to offload such operations to the compositor. The default factor is UINT32_MAX. - This object has to be destroyed before the associated wl_surface. Once the - wl_surface is destroyed, all request on this object will raise the - no_surface error. + If the associated wl_surface is destroyed, all requests except "destroy" + on this object will raise the no_surface error.