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 <contact@kchibisov.com>
This commit is contained in:
Kirill Chibisov 2023-05-31 10:56:58 +03:00 committed by Simon Ser
parent 3c1fb30817
commit 174b3487a2

View file

@ -436,8 +436,10 @@
After creating a role-specific object and setting it up, the client must After creating a role-specific object and setting it up, the client must
perform an initial commit without any buffer attached. The compositor perform an initial commit without any buffer attached. The compositor
will reply with an xdg_surface.configure event. The client must will reply with initial wl_surface state such as
acknowledge it and is then allowed to attach a buffer to map the surface. 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 Mapping an xdg_surface-based role surface is defined as making it
possible for the surface to be shown by the compositor. Note that possible for the surface to be shown by the compositor. Note that