refactor: use InvalidateLayout() not DeprecatedLayoutImmediately()#41899
Closed
refactor: use InvalidateLayout() not DeprecatedLayoutImmediately()#41899
Conversation
Member
Author
|
Pasting CI failures here as breadcrumbs. In order of likely to unlikely, these CI failures may be that the tests were coded to assume synchronous operations, or that this PR really is introducing new bugs, or maybe they're all CI flakes 😜 |
5 tasks
Member
|
@ckerr do you still want to work on this or can we close it for now? |
Member
Author
|
This is still something we need to do; but since I'm not working on it right now, there's no point in keeping this old draft floating around |
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.
Description of Change
Replace our calls to the deprecated API
DeprecatedLayoutImmediately()withInvalidateLayout()instead.It looks like all of the occurrences were just to trigger a new draw & didn't necessarily rely on it happening immediately, so
InvalidateLayout()is the call preferred by upstream.Xref: https://crbug.com/1121681
Xref: https://chromium-review.googlesource.com/c/chromium/src/+/5242027
Checklist
npm testpassesRelease Notes
Notes: none