Important Notice - Forums is archived
To simplify things and help our users to be more productive, we have archived the current forum and focus our efforts on helping developers on Stack Overflow. You can post new questions on Stack Overflow or join our Discord channel.

Vaadin lets you build secure, UX-first PWAs entirely in Java.
Free ebook & tutorial.
Vaadin 8 Tooltip in console font and no linebreaks e.g. in Tabsheet.Tab
Version: 8.0.0.beta2
A Tooltip for a tab displayed in a TabSheet does not line-break and is displayed in a console font.
The possibility to provide ContentMode with setDescription is missing (which fixed for other ToolTips in Vaadin 8)
Other affected components (used so far):
- MenuBar.MenuItem
Sample to reproduce:
final VerticalLayout layout = new VerticalLayout();
layout.addComponent(new Label("Tabsheet Tooltip Linebreak Test with Vaadin Version: " +
com.vaadin.shared.Version.getFullVersion()));
TabSheet sample = new TabSheet();
sample.setHeight(100.0f, Unit.PERCENTAGE);
sample.addStyleName(ValoTheme.TABSHEET_FRAMED);
sample.addStyleName(ValoTheme.TABSHEET_PADDED_TABBAR);
final String toolTipText = "A23456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789";
String tabToolTipText = "";
for (int i = 1; i < 8; i++) {
tabToolTipText = tabToolTipText + " " + toolTipText;
final VerticalLayout tablayout = new VerticalLayout(new Label(
"Tooltip Content: " + tabToolTipText, ContentMode.HTML));
tablayout.setMargin(true);
Tab tab = sample.addTab(tablayout, "Tab " + i);
tab.setDescription(toolTipText);
}
layout.addComponent(sample);
layout.setMargin(true);
layout.setSpacing(true);
setContent(layout);
Created tickets https://github.com/vaadin/framework/issues/8590 and https://github.com/vaadin/framework/issues/8591 for these.
Thank you Henri!
Should issues like these be reported to the forums first so that they can be checked first or is reporting them directly in Github more efficient ? (Currently there are just too many open issues on GitHub to make really sure nothing has been already reported by someone else)
I'd say that if the issue is clearly a bug, there is a straight-forward way to reproduce it and a few quick searches in GitHub issues with relevant keywords don't give an exact duplicate, it can be reported directly in GitHub.