Repository navigation
Wayland-specific handling for platform surface readiness - #21382
Merged
Merged
Conversation
MrJul
enabled auto-merge
May 18, 2026 09:39
MrJul
added this pull request to the merge queue
May 18, 2026
|
You can test this PR using the following package version. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
With Wayland backend we won't have a traditional render timer that ticks at some uniform rate. Instead we have per-window ticks send by the system compositor. Which means that we need to track readiness and wakeups per-surface.
With wayland backend our wayland worker thread IS our render thread and the loop is managed by the backend