-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use MouseEnter/MouseLeave instead of MouseOver/MouseOut #1189
Labels
Comments
React support: https://facebook.github.io/react/docs/events.html |
see #1190 |
#1190 was merged |
mnajdova
pushed a commit
to mnajdova/material-ui
that referenced
this issue
Nov 10, 2020
* install redux and redux-form * configure redux-form * wrap App with redux provider * create redux form example * add react-redux types to dev dependencies * Update docs/pages/guides/form-integration.mdx Co-Authored-By: Dmitriy Kovalenko <[email protected]> * move redux to example folder * Wrap example with redux * remove redux-thunk * modify onChange to allow empty field in the other way, the field always gotten the last valid value, even when explicit deleted. This way, the user can clear the field! * move store to inside Form example
This was referenced Apr 13, 2021
This was referenced Apr 26, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This applies to a lot of components.
This idea is to improve performances by avoiding useless setState.
Let's take the ListItem example.
If a child component is hovered then the hovered state of ListItem switches back and forth even if the list item is still hovered. This creates a lot of useless rerender.
The text was updated successfully, but these errors were encountered: