EGL-Registry EGL_KHR_platform_wayland: Clarify requirements of eglSwapBuffers

The EGL implementation attaching the front buffer, posting damage, and committing during the call to eglSwapBuffers(WithDamage)() is a well established requirement that EGL Wayland clients currently rely upon, thus should be explicitly documented.

I noticed EGL_EXT_platform_wayland already existing, but EGL_KHR_platform_wayland seems to be the one most recently updated. Should this perhaps be targeting that, and with the changes to the KHR variant being ported over?

Sep 09 '24 20:09 jadahl

Context on the motivation for this: https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/423

Sep 09 '24 20:09 amshafer

This version looks good to me.

Sep 10 '24 04:09 cubanismo

Gentle ping - is anything blocking this?

Jan 07 '25 21:01 emersion

Gentle ping, it would be very helpful to clarify this behavior in the spec finally.

Oct 21 '25 15:10 amshafer

Existing clients rely on EGL not creating a wp_color_management_surface_v1. Mesa previously contained a bug where using zink caused such clients to crash because the zink WSI (which delegates to vulkan) did not ensure that this was the case.

The extension should clarify if/when the implementation creates this object.

Oct 23 '25 11:10 mahkoh

Existing clients rely on EGL not creating a wp_color_management_surface_v1. Mesa previously contained a bug where using zink caused such clients to crash because the zink WSI (which delegates to vulkan) did not ensure that this was the case.

The extension should clarify if/when the implementation creates this object.

Added that here: https://github.com/KhronosGroup/EGL-Registry/pull/218 to allow this to land quicker, but could amend it here would so be needed.

Oct 30 '25 15:10 jadahl