Autocomplete: avoid calling setState on input #48565
Merged
Conversation
This file contains 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
|
Size Change: +101 B (0%) Total Size: 1.33 MB
ℹ️ View Unchanged
|
ellatrix
force-pushed
the
fix/autocomplete-guard-set-state
branch
from
f053731
to
ebafb85
Compare
|
Removed the flaky test report because I completely rewrote the PR. |
ciampo
added
[Package] Components
youknowriad
reviewed
Feb 28, 2023
youknowriad
approved these changes
Feb 28, 2023
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.
What?
We're constantly flipping state from false to true on input. I actually introduced this perf regression a while back, apologies. 🙈
Why?
How?
Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast