JDK-8299755 : Tree/TableView: Cursor Decouples From Divider When Resizing With Fractional Scale
  • Type: Bug
  • Component: javafx
  • Sub-Component: controls
  • Affected Version: jfx20
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows
  • Submitted: 2023-01-06
  • Updated: 2025-03-21
  • Resolved: 2025-03-04
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.
Other
jfx25 b07Fixed
Related Reports
Blocks :  
Relates :  
Relates :  
Relates :  
Description
The Windows HiDPI behavior (on my system with a screen scale of 1.25) with a policy of NEXT or LAST, the divider tracks the mouse cursor as expected.

With a policy of FLEX_NEXT or FLEX_LAST, it tracks until the first (or last) column being resized hits its minimum and it switches to another column. Similarly, with a policy of SUBSEQUENT, it doesn't quite track as expected when one of the columns gets small (i.e., close to its minimum). This might just be error accumulation. It seems like a minor problem.

The issue can be reproduced on Windows by setting fractional scale:

Windows 11:
Settings -> System -> Display -> Scale -> 125% (or 225% ...)

Please refer to the attached video clips.  At scale 1.0, the cursor tracks the divider.  At scale 1.25, the courser decouples from the divider at some point.
Comments
Changeset: 1824db5c Branch: master Author: Andy Goryachev <angorya@openjdk.org> Date: 2025-03-04 15:33:29 +0000 URL: https://git.openjdk.org/jfx/commit/1824db5c7183b5b3749fe4c29baae51f34dcc421
04-03-2025

A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jfx/pull/1156 Date: 2023-06-15 19:38:00 +0000
09-07-2024

Changing to a P4 bug after a conversation with [~kcr].
13-07-2023