On Tue, 2 Sep 2025 21:56:50 GMT, Nir Lisker <[email protected]> wrote:
>> This PR adds the release notes for the JavaFX 25 release. This will first go >> into master, and then be backported to the jfx25 branch so it will be >> available in that branch when JavaFX 25 is published (and from there also >> synced into the jfx25u repo). >> >> The following filter was used to produce the list of issues fixed in JavaFX >> 25: >> >> https://bugs.openjdk.org/issues/?filter=47140 >> >> Additionally, we had four issues with a `release-note=yes` label, which are >> included in the list of important changes, etc. > > doc-files/release-notes-25.md line 139: > >> 137: [JDK-8352162](https://bugs.openjdk.org/browse/JDK-8352162) | Update >> libxml2 to 2.13.8 | web >> 138: [JDK-8352164](https://bugs.openjdk.org/browse/JDK-8352164) | Update >> libxslt to 1.1.43 | web >> 139: [JDK-8353916](https://bugs.openjdk.org/browse/JDK-8353916) | Unexpected >> event type for DOM mutation events with WebKit 620.1 | web > > There are various issues fixed for WebKit 620.1 while only in this JavaFX > version that WebKit version was introduced. Is it really meaningful to > specify them? Yes, these should be excluded for the same reason as the ones Michael pointed out above: they are transient bugs that were introduced and fixed in the same version, so will not be seen by anyone migrating from jfx24 to jfx25. I'll add a `javafx-rn-exclude` label to the 5 follow-on WebKit 620.1 bugs (setting the "introduced-in-release" field won't do it for these, since that would be the update release of the earliest release family). ------------- PR Review Comment: https://git.openjdk.org/jfx/pull/1871#discussion_r2319338259
