Remove 'selectedValues' or clarify its relationship to `value`

[evert]

selectedValues has the same purpose as value. Both properties show the pre-filled value of the property before the user starts editing.

I hope we can remove selectedValues and use value for all these cases. If not, I think the spec could benefit from some clarification on how they relate to each other. What happens if both are provided?

[mamund]

if i recall correclty, the current state of affairs has to do w/ the original definition of value as a string and selectedValues as an array. we wanted to support multiple values and i did not want to introduce a compatibility -breaking change to the interface by changing value to an array.

i think i even suggested an option where the value contents could be a JSON.stringify-like array value but that was not popular.

i prefer there be just value and not have the selectedValues. there may be other ways to solve this as a non-breaking change but i have not yet found one that is acceptable.

ideas?