Implement a RTL support for client side "helper" widgets

[vaadin-bot]

Originally by @johannest

---

Implement a RTL support for the client-side "helper" widgets. At least widgets below have to supported. Assumed changes/tasks are listed below of each widgets.

VTooltip & TooltipInfo

• get direction from owner (if it is HasDirection) by implementing setOwner
• description element css
• testing (manual and TB tests) VErrorMessage
• get direction when setOwner is called
• RTL css
• testing (manual and TB tests) VCaption
• get direction from owning component
• mirrored Icon placement
• css for captionText
• css for errorIndicatorElement and requiredFieldIndicator
• testing (manual and TB tests) com.vaadin.client.ui.FontIcon and ImageIcon
• css
• testing (manual and TB tests) VOverlay
• ???
  VLoadingIndicator
• mirrored
• testing (manual and TB tests) VContextMenu
• get direction from actionOwner??
• CMenuBar
  • show menu on the left side of the cursor
  • open nested menus on the left side (can there be nested context menus??)
  • css for menu item
  • icons on the right side
• testing (manual and TB tests) vaadin.client.ui.Action
• get direction from actionOwner??
• icon and caption reversed + css for caption
• testing (manual and TB tests) VUI / UIConnector
• direction for loading indicator
• direction for notifications

---

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

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