JDK-8117558 : Tooltip layout issue in RTL orientation.
  • Type: Bug
  • Component: javafx
  • Sub-Component: controls
  • Affected Version: 8
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2012-11-09
  • Updated: 2015-06-17
  • Resolved: 2013-03-16
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8
8Fixed
Related Reports
Blocks :  
Relates :  
Relates :  
Description
Apply the sdk in the 8.0 controls repo. (hudson build #110) which contains the fix for RT-138/RT-24235, run Tooltip testcase, there are 2 problems in RTL orientation:
1. The tooltip still appears on the right side, please refer to the attached image"tooltip-bent.png". According the spec, it should appear on the left side.
2. When "textOverrun" is "CLIP" and the font size is quite large, for example 30, the text and tooltip panel are separated. Please refer to the attached image"tooltip-large-font.png". This doesn't happen in LTR orientation.

Comments
close the bug as it has been verified in b82.
21-10-2013

No additional test case needed. It has been covered by existing test.
05-06-2013

Jenny - do we need any additional test on that?
04-06-2013

Verified fix for the first issue in b82. For the second issue, it looks to be same as RT-27764, updated that bug for Tooltip.
25-03-2013

Changeset: http://hg.openjdk.java.net/openjfx/8/controls/rt/rev/148a5ddb6d8d The tooltip now always inherits the nodeOrientation of the Node that it is attached to. It is possible to override this for the Tooltip content (but not the popup placement) by setting the nodeOrientation on tooltip.getScene().getRoot(). The second issue listed is probably a separate problem. Please file a new JIRA issue if it is still reproducible.
16-03-2013