-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[BUG] search_value triggers unrelated callbacks, making dropdown search unusable #2428
Comments
Duplicate of #2411 |
Fixed along with #2411 |
I have just used an example provided by @oegedijk in Dash 2.9.2 and the problem is still there. |
Same thing here, having the problem still in 2.9.2 |
@T4rk1n could we add a failing test for this so that it will get fixed in the next release? |
I believe this is fixed in Dash v2.10.2 |
Indeed, fixed in 2.10.1 |
While chasing down a bug in explainerdashboard, I noticed that when you have a dynamic server side dropdown search, and also have a callback targeting dropdown.value, then this latter gets triggered everytime you search in the dropdown. Usually with unwanted side effects. In this case it makes the dropdown search completely unusable.
Below an example, with a dropdown, and a select random item button. Searching in the dropdown triggers the button callback. Including a callback.context check to see if the button callback was indeed triggered by the button n_clicks input seems to fix the problem.
The text was updated successfully, but these errors were encountered: