JDK-8090456 : Focus Management
  • Type: Enhancement
  • Component: javafx
  • Sub-Component: controls
  • Affected Version: 7u15
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2013-06-26
  • Updated: 2024-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
Related Reports
Relates :  
JDK-8292933 - Multiple focused components accepting keyboard input
Relates :  
JDK-8091673 - Public focus traversal API for use in custom controls
Relates :  
JDK-8091670 - Add API for better control over keyboard focus
Relates :  
JDK-8091594 - Documentation on the Focus Traversal Policy in JavaFX 2.0
Relates :  
JDK-8091524 - Introduce a "focus container" concept in class Parent
Description
We need a public API for defining hierarchical compositions of focus cycles in a view including the declaration of focus cycle root elements (like we have in SWING). 

Proposal:
https://github.com/andy-goryachev-oracle/Test/blob/main/doc/FocusTraversal/FocusTraversal.md
Comments
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jfx/pull/1555 Date: 2024-09-03 19:09:15 +0000
09-09-2024
I second that. We need an API to manually change focus using the focus traversal engine. It is not sufficient to use the TAB key to e. g. move from one textfield to another. People like to use different keys, e. g. the ENTER key. Moreover it should be possible to prevent focus change if the value in e. g. a textfield isn't valid. There is already a method "traverse" for the scene, but that one's not accessible. Neither is the method impl_traverse of the nodes. Well, it's public, but deprecated and will most probably be removed, so we can't use that one.
01-05-2015