broken after multiple scroll up/downĪpplication freezes when copying an animated gif image to the system clipboardĮxception printed to stdout on Windows when storing transparent image in clipboard
Wrong visible amount in Adjustable of ScrollPane Linux: NullPointerException from FontConfiguration.getVersion in case no fonts are installed
Ideographic characters aren't stretched by AffineTransform.scale(2, 1) On the latest macOS+XCode the Robot API may report wrong colors However, these applications would also prefer to use the same command line across multiple versions of the JDK, especially if it is not known what JDK version a user will use.Ĭurrently, if these options are specified in JDK 12 or earlier, the runtime attempts to load a SecurityManager implementation with the classname 'allow' or 'disallow', which results in a Could not create SecurityManager Error and the application will not start up.įrom this release onward, the 'allow' and 'disallow' options for the system property will be ignored. For those that enable the SecurityManager at runtime via tSecurityManager, they have to specify the 'allow' option as of JDK 18 (see JDK-8203316). Many applications and frameworks are designed to run on multiple JDKs. In JDK 12, two new token options for the system property, 'allow' and 'disallow', were introduced. Security-libs/curity ➜ Ignore Allow and Disallow Options for System Property
