In the example for getValue() it shows a Choices instance being initialized from a HTML element.
I think this is misleading because it makes the user think that they can access the values with getValue() by simply initializing using an HTML element. But if you try to initialize on an element that was already initialized it won't work. And if you make a completely new Choices instance there will only be the default values.
I think it would be better if the example code showed using getValue() on a Choices instance that was saved in a variable and/or explains that to get the values from an existing element you will have to save its Choices instance in a variable that you can access in your code later – multiple issues were opened because users did not understand this.
(This problem might apply to other functions as well)
In the example for getValue() it shows a Choices instance being initialized from a HTML element. I think this is misleading because it makes the user think that they can access the values with getValue() by simply initializing using an HTML element. But if you try to initialize on an element that was already initialized it won't work. And if you make a completely new Choices instance there will only be the default values.
I think it would be better if the example code showed using getValue() on a Choices instance that was saved in a variable and/or explains that to get the values from an existing element you will have to save its Choices instance in a variable that you can access in your code later – multiple issues were opened because users did not understand this.
(This problem might apply to other functions as well)