-
Bug
-
Resolution: Fixed
-
P2
-
8
-
$ java -version
java version "1.8.0_20-ea"
Java(TM) SE Runtime Environment (build 1.8.0_20-ea-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.20-b12, mixed mode)
The project has two (main) files hosted on a webserver http://localhost:8080/
- login.fxml
- login.css
The FXML references the CSS file as:
<stylesheets>
<URL value="@login.css"/>
</stylesheets>
The FXMLLoader is created pointing to the remote URL "http://localhost:8080/login.fxml". JavaFX loads correctly both the FXML structure and the CSS.
The application has a button that removes the created Node, and calls FXMLLoader again, causing a reload of the FXML/CSS (and other resources). Most changes are correctly processed, like FXML structures and inline style. The problem occurs when the CSS file is updated on the server, and due to perhaps a problem inside StyleManager, the CSS cache is not correctly cleaned.
To test, there is a sample FXML and CSS application here: https://github.com/brunoborges/webfx/tree/master/webfx-samples/src/main/webapp/login
Javascript-based FXML controller is loaded correctly as well. The problem is limited to the CSS file not being picked up with the new changes.
- login.fxml
- login.css
The FXML references the CSS file as:
<stylesheets>
<URL value="@login.css"/>
</stylesheets>
The FXMLLoader is created pointing to the remote URL "http://localhost:8080/login.fxml". JavaFX loads correctly both the FXML structure and the CSS.
The application has a button that removes the created Node, and calls FXMLLoader again, causing a reload of the FXML/CSS (and other resources). Most changes are correctly processed, like FXML structures and inline style. The problem occurs when the CSS file is updated on the server, and due to perhaps a problem inside StyleManager, the CSS cache is not correctly cleaned.
To test, there is a sample FXML and CSS application here: https://github.com/brunoborges/webfx/tree/master/webfx-samples/src/main/webapp/login
Javascript-based FXML controller is loaded correctly as well. The problem is limited to the CSS file not being picked up with the new changes.