Component description (tooltip) can't have custom delay

[Thibstars]

Vaadin 8.0.6

When a component (Label for example) has a description (example call: label.setDescription("Hello World!");), the delay of the tooltip to become visible isn't directly adjustable.

The only way you can adjust delays (I see at this moment) , is by adjusting the delay of the ToolTipConfiguration of the UI. But that is not really doing what I'm suggesting here.

I would expect some method on Component level that provides means to adjust the delay for the component's tooltip to become visible.

[Legioth]

In what kind of case would you want to have different timeouts for different components?

[Thibstars]

Well, I have a component in my application that contains tiny pagination control components (buttons with only 1 VaadinIcon, styled as links, so they're pretty small). Since the tooltips are hovering over the other controls, I'd like to add more delay for these specific components.

The controls should be pretty straight forward, so normally you wouldn't need to check the description. However it is provided for those who really need it. That's why I reckon the tooltips should only appear when the user really wants to see them.

Hope that makes a bit of sense.

[EDIT] Let me empower my use case with a screenshot:

[stale[bot]]

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!