Repository navigation
fix: relayout after rejecting oversized images - #7314
Merged
Merged
Conversation
pajlada
approved these changes
Sep 26, 2026
pajlada
enabled auto-merge (squash)
September 26, 2026 12:21
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.
When an image from a set exceeds the memory limit it is marked as empty but no relayout is triggered. This means the fallback image is not loaded until a relayout happens incidentally from somewhere else, and it leaves a blank space in the meantime. This affects twitch gifs where
200.webpis rejected as oversized, so it falls back to100.webp.Fixed by forcing a relayout after marking the image as empty.