-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
onMenuOpen triggers on each input #3335
Comments
I confirm the bug with react-select@2.4.1 in Chrome 72 |
Any update on this? |
still on 3.0.4. The |
Still the same behavior in 3.0.8 The react-select/packages/react-select/src/Select.js Line 1092 in 3c7de0d
|
…utChange in Select.js
Well just removing the call to |
…selectors on a single page - Only perform onMenuOpen / onMenuClose if the menu is actually closed / open. -- Will invalidate PR JedWatson#3897 / Issues JedWatson#3335 JedWatson#3620
…utChange in Select.js
pruik found that we should call The PR now passes all the test 🎉 |
PR #3335 in review. |
Fixes #3335 - removes the call to onMenuOpen within handleInputChange
When a select (or creatable) is open, writing triggers onMenuOpen callback on each keystroke.
Demo: https://codesandbox.io/s/k0l8r2z6yr
I think that it should only trigger when opening the menu, right?
The text was updated successfully, but these errors were encountered: