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>
Kirill Chibisov authored 10 months ago
Simon Ser committed 9 months ago
| 435 | 435 | |
| 436 | 436 | After creating a role-specific object and setting it up, the client must |
| 437 | 437 | perform an initial commit without any buffer attached. The compositor |
| 438 | will reply with an xdg_surface.configure event. The client must | |
| 439 | acknowledge it and is then allowed to attach a buffer to map the surface. | |
| 438 | will reply with initial wl_surface state such as | |
| 439 | wl_surface.preferred_buffer_scale followed by an xdg_surface.configure | |
| 440 | event. The client must acknowledge it and is then allowed to attach a | |
| 441 | buffer to map the surface. | |
| 440 | 442 | |
| 441 | 443 | Mapping an xdg_surface-based role surface is defined as making it |
| 442 | 444 | possible for the surface to be shown by the compositor. Note that |