[Select][base] Do not call onChange after initial render #37141
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
michaldudak
added
bug 🐛
Netlify deploy previewhttps://deploy-preview-37141--material-ui.netlify.app/ Bundle size report |
mj12albert
reviewed
May 9, 2023
Signed-off-by: Albert Yu <albert@albertyu.co>
mj12albert
approved these changes
May 9, 2023
binh1298
pushed a commit
to binh1298/material-ui
that referenced
this pull request
May 17, 2023
Signed-off-by: Albert Yu <albert@albertyu.co> Co-authored-by: Albert Yu <albert@albertyu.co>
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 the Select's value (controlled or uncontrolled) was set to
null, theonChangeevent handler was called right after the initial render. This PR fixes this behavior and adds tests for various related cases.Fixes #36783