Table header texts are not shown anymore when theme is switched from Valo to non-Valo theme

[vaadin-bot]

Originally by winfried.stenzel

---

When the theme is changed from a Valo theme to a non-Valo theme, table header texts are not shown anymore.

Steps to reproduce:

• go to vaadin table sampler (http://demo.vaadin.com/sampler/#ui/data-presentation/table)
• change the theme to Reindeer (or Runo or Chameleon) by clicking on the editor button and the tab "Theme"

The table header texts ("Country", "Code") are not shown anymore.

This happens with Firefox 33.0.1 and Internet Explorer 11.

Assumption: In my application the header captions do appear even for Reindeer, Runo and Chameleon if one of these themes is the theme used for the @Theme annotation, i.e. as initial theme. There seems to be a problem in UI.setTheme(). Perhaps some sort of cache/initialization is not updated?

---

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

[vaadin-bot]

Originally by @Legioth

---

Seems like the column widths are not properly reinitialized, which in turn causes the actual text to wrap to a new line, below the actual header location.

Removing overflow: hidden from the .v-table-caption-container element seems to hide the problem, but doing this might have unintended effects in other situations.

[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!

[stale[bot]]

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!