Dropdown gets triggered even if value does not change #680
Replies: 5 comments
-
@gaborfodor This is by design. All the components on a page submit their values, independent of the dropdown's Normally, the buttons on a page are the canonical way to send information from the browser to the app. But in some cases, you might want to get that information as soon as the value of a component changes (saves the user from the additional step of having to click some button) - hence the
It's simply a flag for "should information be submitted when the value changes?" - and not "only when the value changes". |
Beta Was this translation helpful? Give feedback.
-
Thanks, that makes sense.
|
Beta Was this translation helpful? Give feedback.
-
I've just hit this bug in a funny way dropdown_bug.movI'm afraid @gaborfodor 's trick would not work for me, unless I set the dropdown value to None in q.client. |
Beta Was this translation helpful? Give feedback.
-
This means we need to ensure there is a hierarchy on the way |
Beta Was this translation helpful? Give feedback.
-
I understand the design though :) |
Beta Was this translation helpful? Give feedback.
-
Wave SDK Version, OS
0.11.0 Mac
(e.g. 4.2.0, Windows)
Actual behavior
I have a single button and a dropdown menu. The dropdown menu gets triggered too when I press the button.
Expected behavior
According to doc I expected it to get triggered only when the value changes.
"trigger: True if the form should be submitted when the dropdown value changes."
Steps To Reproduce
Beta Was this translation helpful? Give feedback.
All reactions