JDK-8092211 : Promote all skin and behavior classes of the default controls to the public API
  • Type: Enhancement
  • Component: javafx
  • Sub-Component: controls
  • Affected Version: 8u40
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2015-03-27
  • Updated: 2018-09-05
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-8186137 - [JavaFX 9] TextFieldSkin, MenuButtonSkinBase - behavior can't be passed
Relates :  
JDK-8091189 - Move BehaviorBase into public API
Description
At the current moment all skins and behaviors for the default controls are residing in the com.sun.javafx.* package. As far as I understand it will not be possible to access that package anymore with version 9, so not possible to access these skins and behaviors.

However, using the existing skin and behavior classes is extremely useful especially when customizing the default controls or extending them to create new ones. Not being able to access the skins and behaviors of the default control would make it close to impossible to extend upon these controls, as it would require to rewrite the complete skin and behavior and then extending that one.

So in the vein of RT-21596 I request that these are promoted to the public API for 9.

Additionally I'd like to note that if they are promoted to the public API, that the skins should receive an additional public constructor the accepts the behavior. See RT-40150 for that one.
Comments
This is currently being considered, exactly for the reasons you stated. However, to be clear, the thinking around behaviors is more in line with RT-21598, rather than simply making them public. Therefore, I'll leave this issue open, and will eventually repurpose it, once our thinking is more fleshed out.
29-03-2015