Conversation
SLINT_BACKEND selects a renderer by name, but an unavailable renderer falls back silently instead of erroring, so a screenshot can come from a different renderer than the one requested without any indication.
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
1 participant
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.
`SLINT_BACKEND` selects a renderer by name (e.g. `winit-skia`), but an unavailable renderer falls back silently instead of erroring — a binary built without `renderer-skia` compiled in still accepts `SLINT_BACKEND=winit-skia` and renders with whatever it does have, with no indication a fallback happened.
Adds a short section to `docs/development/mcp-server.md` covering the `nm -gU | grep -c i_slint_renderer_skia` check to confirm which renderer actually linked, and a reminder to confirm the state change under test actually reached the application before treating "no pixel diff" as a rendering bug.
Test plan