-
Notifications
You must be signed in to change notification settings - Fork 448
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
UI dropdown - Unable to set a preselected option #675
Comments
Sorry - I don't think I understand the problem correctly - A simple test like this works for me
Can you share a simple example that shows your actual issue ? |
Hi, I've just tried your flow: it stops working if you turn off the option "If msg arrives on input, pass through to output".
Thanks |
indeed - if the message doesn't pass through then it won't set the selected option. |
But the intent is not to send over the message but only to update the UI. Until the previous release it worked in this way and, in fact, the documentation doesn't say that the "pass through" must be enabled in order to update the UI. |
true - looking at it now. |
As this is closed I guess its solved from 2.28.0 on? Right? |
@number005 yes. The commit that closed this issue was included in 2.28 |
What are the steps to reproduce?
Send a msg (with a string in msg.payload) to a dropdown node.
What do you expect to happen & what happens?
Until the release 1.2.5, the dropdown node was correctly updated with the text contained in the received payload.
With the new release (1.2.7) this does not happen.
Please tell us about your environment:
The text was updated successfully, but these errors were encountered: