Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P3
Fix Version/s: 8u40
Affects Version/s: 8u5, 8u20
Component/s: javafx
Labels:
- api
- api-request

Subcomponent:
controls

I've seen a lot of reports recently (most recently in the ControlsFX project here: https://bitbucket.org/controlsfx/controlsfx/issue/370/using-controlsfx-causes-css-errors-and ) about JavaFX custom controls showing runtime warnings and visual glitches. This seems related to the use of Control.getUserAgenetStylesheet(), which is not something we use in JavaFX itself, but which is used by third party controls to bring in custom stylesheets. After discussing with David it seems best to improve the CSS engine to improve the handling of this code, and to isolate the stylesheets brought in by a Control such that they only impact themselves and their children. This prevents a bad stylesheet breaking other aspects of the UI. This seems both reasonable and sensible.

relates to

JDK-8091109 getUserAgentStylesheet() gives poor support for OOP because it does not work with inheritance

Open

JDK-8092530 Behavior and access of Control#getUserAgentStylesheet method changed in 8u40

Resolved

JDK-8092984 Compile error with 8u40 since Region#getUserAgentStylesheet() was made public

Closed

JDK-8133831 findMatchingStyles/User agent precedence

Open

Assignee:: David Grieve

Reporter:: Jonathan Giles

Votes:: 4 Vote for this issue

Watchers:: 6 Start watching this issue

Created:: 2014-09-11 13:56

Updated:: 2015-10-19 15:20

Resolved:: 2014-09-18 12:31

Imported:: 12/Jun/15 4:39 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates