>From my limited testing, the issue is still present in 8u172 b03 (early access) and 9.0.1+11 (that is, assuming it is the same bug which I am crossing my fingers about!).
Thanks for taking this back up, John. On Fri, Feb 23, 2018 at 4:45 PM, Kevin Rushforth <kevin.rushfo...@oracle.com > wrote: > > In general, what should we do when we find bugs in version 8 but the >> latest development is happening on version 11? Open the bug, or test it >> against the latest version first? >> > > The latter is preferable if it is possible to test it on the latest > version. > > Thanks. > > -- Kevin > > > > John Neffenger wrote: > >> On 02/23/2018 02:29 PM, Michael Ennen wrote: >> >>> Here is the issue: >>> >>> https://gitlab.com/openjfxepd/jfxpatch/issues/1 >>> >>> Thanks to John Neffenger for taking the time to put this together! I >>> wanted to make this work was known to Kevin and the team. >>> >> >> I'm so glad you found it! I posted a link to the issue, along with two >> others, on this mailing list a year ago, but I think people were too busy >> with all the Java 9 changes happening at the time (rightfully so). >> >> I was reluctant to open the official bugs on the Oracle page before >> testing whether they still occur in the latest version. Actually, I haven't >> even had the time to check whether they still occur in the latest OpenJFX 8. >> >> In general, what should we do when we find bugs in version 8 but the >> latest development is happening on version 11? Open the bug, or test it >> against the latest version first? >> >> Thanks, >> John >> > -- Michael Ennen
