Selection issue for only Spaces in Treen node name

[vaadin-bot]

Originally by vinodvaadin

---

Hi Team,

Just having spaces in the tree node name, does not allow selection of such a tree node.

The issue is seen when a tree node having a regular name is renamed to a name that only has spaces e.g - " ". Once tree node has only spaces, it does not get selected.

Below is a sample example of a Tree where root is "Book" and its children are "Novel", "Fiction", "Animation", and "Games"

Book

• "Novel"
• "Fiction"
• "Animation"
• "Games"

Over here if we rename the 2nd children "Fiction" to " ". Selection on the 2nd node does not work.

Book

• "Novel"
• " "
• "Animation"
• "Games"

---

Imported from https://dev.vaadin.com/ issue #20430

[vaadin-bot]

Originally by @Legioth

---

The cause of this seems to be that the the <span> that has the click listener has zero height when there is no content.

Until this has been fixed in the framework, you can work around it in your own theme by defining a suitable height (or min-height) for e.g. .v-tree-node-caption > div > span.

[stale]

A lot of tickets have been left hanging in the issue tracker through the years. Some of them are still relevant, some of them have been fixed a long time ago and some are no longer valid. To get a better look on what is important and still relevant, we are closing old tickets which have not been touched in a long time. No further work will be done on this ticket. If the ticket seems to be still actual, please verify the problem existence over latest framework version and then open a new ticket in vaadin/framework with all the suitable information.

[stale]

Hello there!

We are sorry that this issue hasn't progressed lately. We are prioritizing issues by severity and the number of customers we expect are experiencing this and haven't gotten around to fix this issue yet.

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!