Avoid calling performLayout when only the relayout boundary is different#99056
Merged
fluttergithubbot merged 4 commits intoflutter:masterfrom Mar 9, 2022
Conversation
bd50354 to
b1ffd1e
Compare
74050d8 to
51ef6ff
Compare
…ut-on-relayout-boundary-changes
51ef6ff to
f506e5f
Compare
goderbauer
approved these changes
Mar 7, 2022
Comment on lines
+57
to
+59
| set layoutCount(int newValue) { | ||
| renderObject.layoutCount = newValue; | ||
| } |
Member
There was a problem hiding this comment.
Do you need this setter? Maybe remove it since it is a bit doggy.
Member
There was a problem hiding this comment.
I'd probably also remove the getter as well and just obtain the current layoutCount value in the test with tester.renderObject<RenderLayoutCount>(find.byType(RenderLayoutCount)).layoutCount. Currently the test reads a little strange with getting the layoutCount off a widget...
Contributor
Author
There was a problem hiding this comment.
Switched to WidgetToRenderBoxAdapter instead
…ut-on-relayout-boundary-changes
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Mar 9, 2022
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/plugins
that referenced
this pull request
Mar 9, 2022
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Mar 9, 2022
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Mar 9, 2022
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Mar 9, 2022
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Mar 9, 2022
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Mar 9, 2022
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Mar 11, 2022
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Mar 11, 2022
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Mar 11, 2022
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Mar 12, 2022
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Mar 14, 2022
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Mar 14, 2022
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Mar 14, 2022
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Mar 14, 2022
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Mar 14, 2022
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Mar 14, 2022
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Mar 14, 2022
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Mar 14, 2022
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Mar 14, 2022
9 tasks
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.
In theory a render subtree shouldn't redo its layout if the incoming constraints are the same and nothing in the tree is dirty. Whether a node is a relayout boundary (or who its relayout boundary is) isn't really "inherent" and shouldn't affect the subtree's layout.
This pull request:
RenderObject.layoutfrom aggressively marking everything dirty in a subtree until the next relayout boundary is reached (instead mark everything dirty until the closest known repaint boundary inRenderObject.markNeedsLayout).Pre-launch Checklist
///).If you need help, consider asking for advice on the #hackers-new channel on Discord.