Skip to content

wayland: don't send set_buffer_scale on wl_surface below version 3#4622

Merged
ogoffart merged 1 commit into
rust-windowing:masterfrom
slint-ui:olivier/wayland-cursor-buffer-scale
Jul 9, 2026
Merged

wayland: don't send set_buffer_scale on wl_surface below version 3#4622
ogoffart merged 1 commit into
rust-windowing:masterfrom
slint-ui:olivier/wayland-cursor-buffer-scale

Conversation

@ogoffart

@ogoffart ogoffart commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

wl_surface::set_buffer_scale is available since version 3. Sending it on an older surface is a protocol error that terminates the connection. This could happen when setting a custom cursor on a compositor without wp_viewporter. The neighboring damage call already checks the version.

wl_surface::set_buffer_scale is available since version 3. Sending it
on an older surface is a protocol error that terminates the connection.
This could happen when setting a custom cursor on a compositor without
wp_viewporter. The neighboring damage call already checks the version.
@ogoffart ogoffart requested a review from kchibisov as a code owner July 9, 2026 09:55
@ogoffart

ogoffart commented Jul 9, 2026

Copy link
Copy Markdown
Contributor Author

Note: this wasn't tested. This just came up as I scanned the code with AI tools in the context of reviewing another PR, and wanted to verify what was the lower version of the protocol we support unconditionally.
But this seems to be a bug rather than a statement that we don't support version 2 anymore.

@kchibisov kchibisov left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's ok, but doubt v3 exists, most things mandate something recent.

@ogoffart ogoffart merged commit ca573df into rust-windowing:master Jul 9, 2026
49 of 50 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants