-
Notifications
You must be signed in to change notification settings - Fork 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
Dropdown: calls onChange
even when value is not changed
#3437
Comments
What is also worth mentioning is that this doesn't happen if you actually select an option from the list by clicking it. |
It comes from #3391 that fixes #3370. @mic4ael Can you please describe steps more detailed? I've made another codesandbox (https://codesandbox.io/s/jpnzzkl7pv), actually behavior looks correct to me. |
In that case that is partially broken because just like I mentioned, this doesn't happen when you actually click the option instead of clicking outside of the dropdown. |
Result is that
Result is that |
Actually, it's a wrong behavior, you can compare it with a native
So the value is not changed on these steps, right? Actually, it's a correct behavior, see #3370. |
So, at least I think that the first case I presented is a bug, right? |
Yep, we should not call Steps
Expected result
Actual result
|
onChange
onChange
even when value is not changed\
onChange
even when value is not changed\onChange
even when value is not changed
I would like to work on this one if there are no objections. |
Feel free to pick up it 👍 |
sorry @mic4ael if you're working on this |
Bug Report
Steps
Expected result
onChange
was called once as value wan't changed. The native<select />
has the same behavior.Actual result
onChange
was called twice.Version
0.85.0
Testcase
https://codesandbox.io/s/jpnzzkl7pv
The text was updated successfully, but these errors were encountered: