It does, yes. That was triple-checked and the select values go from 1-10, trying to set any of those still doesn’t set the value correctly. And using inspect element I can see the value in the select is correct.
What is the exact setvalue code you are using? Note that the input values are always strings, so you maybe just don’t send a string with the setvalue action.
Not sure how can this be improved in any way. When you enter the 2 value in the UI it’s considered a number, but the inputs values are always strings. Which means 2 is not equal to '2'
Maybe @patrick can check if we can improve the
value comparison when using setvalue for elements like select menus.
Stumbled upon this too.
Thanks to this discussion, I now understand why it happens and how to solve this.
I get the logic behind this behavior, but I have to agree with @Digo , that it would be good to have some built-in seamless solution for this.
Just to reduce the confusion for users, who don’t know about this issue.