From 174b3487a2ac33d6f93f5313b5eccd65db2a2f12 Mon Sep 17 00:00:00 2001 From: Kirill Chibisov Date: Wed, 31 May 2023 10:56:58 +0300 Subject: [PATCH] stable/xdg-shell: clarify initial wl_surface acknowledgement Clarify how and when initial wl_surface state provided by the core protocol or by extensions to the wl_surface, like as wp_fractional_scale_v1, is being delivered. The motivation for such change is to make it clear that the first frame for xdg-shell will be perfect, which implies that scaling and similar properties affecting presentation would be delivered in time. Signed-off-by: Kirill Chibisov --- stable/xdg-shell/xdg-shell.xml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/stable/xdg-shell/xdg-shell.xml b/stable/xdg-shell/xdg-shell.xml index b83c129..777eaa7 100644 --- a/stable/xdg-shell/xdg-shell.xml +++ b/stable/xdg-shell/xdg-shell.xml @@ -436,8 +436,10 @@ 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. + will reply with initial wl_surface state such as + wl_surface.preferred_buffer_scale followed by 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