JDK-8091337 : [TextInputControl] Provide caretBlinkRate property
  • Type: Enhancement
  • Component: javafx
  • Sub-Component: controls
  • Affected Version: 8u25
  • Priority: P3
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2014-12-16
  • Updated: 2018-10-18
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
tbdUnresolved
Description
In Swing you could set the blink rate of caret as:

JTextComponent c = new JTextArea();

// Set rate to blink once a second
c.getCaret().setBlinkRate(1000);

// Set the caret to stop blinking
c.getCaret().setBlinkRate(0);

But in JavaFX there are no available methods to set the blink rate of caret. It would be nice if there is a caretBlinkRate property which does this.
Comments
The following additional information is copied from https://github.com/javafxports/openjdk-jfx/issues/253 "JavaFX uses a fixed caret blink rate, instead of following the OS settings that users expect to control this behavior. In particular, the inability to disable this animation is an accessibility problem for some of our users, so we need to change it. Swing ... [provides ability to change caret blick rate] in two ways: there are methods to set the blink rate on individual text controls, and also UI properties to configure them globally. Either would meet our use case, although a global setting would be simpler to use, since I'd imagine most users will expect the same blink rate to be applied to all controls at once. Another option is to treat it as a styling property: e.g. RichTextFX allows its caret blink rate to be configured with CSS."
18-10-2018
Raising priority to P3 since there are accessibility concerns associated with this RFE.
18-10-2018