Vaadin 8: NativeSelect not allowing empty codes shows selection while empty

[sergetania]

1. Create a NativeSelect field
2. Populate it with a list of items for the user to select from
3. Set it to not allow empty codes.
4. Set its value to empty
5. Observe that the combo will display the first item from the list (in Vaadin 7 it used to remain empty)
6. The value of the combo will be empty.... but the combo on the page WILL SHOW that the first item is selected!

Why does it show a selected item if its value remains empty? How is the user supposed to select the first item then? It should either show blank on the page like it did in Vaadin 7(compatibility is good!) or populate the combo value with the selected item.

To see the problem using the attached project, go to
http://localhost:8080/v8-nativeselect/#!View
v8-nativeselect.zip

[stale]

Hello there!

It looks like this issue hasn't progressed lately. There are so many issues that we just can't deal them all within a reasonable timeframe.

There are a couple of things you could help to get things rolling on this issue (this is an automated message, so expect that some of these are already in use):

• Check if the issue is still valid for the latest version. There are dozens of duplicates in our issue tracker, so it is possible that the issue is already tackled. If it appears to be fixed, close the issue, otherwise report to the issue that it is still valid.
• Provide more details how to reproduce the issue.
• Explain why it is important to get this issue fixed and politely draw others attention to it e.g. via the forum or social media.
• Add a reduced test case about the issue, so it is easier for somebody to start working on a solution.
• Try fixing the issue yourself and create a pull request that contains the test case and/or a fix for it. Handling the pull requests is the top priority for the core team.
• If the issue is clearly a bug, use the Warranty in your Vaadin subscription to raise its priority.

Thanks again for your contributions! Even though we haven't been able to get this issue fixed, we hope you to report your findings and enhancement ideas in the future too!

[mstahv]

You should call setValue(null), not setValue("") if you want to have it as undefined initially. Then it works as expected.