Repository navigation
Keep layout requests from different widgets separate while held - #96
Merged
Merged
Conversation
trissim
changed the title
trissim
deleted the
perf/scroll-parent-coordinate-acquisition-20261007
branch
October 11, 2026 20:05
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.
messages.Layout.can_replacenow only replaces a pending layout message from the same widget, so one widget's request no longer swallows another's.Screengets_has_actionable_layout_requests, used by the scroll path, and after a held subtree is released its pending request now sets_layout_requiredand schedules an idle check.widget.pyis also changed for nested scroll coordinates, and three test files are updated.