JxBrowser

We are very happy to announce JxBrowser 6.21 version.

Chromium 64-bit on Windows

Since 6.21, JxBrowser distribution package includes Chromium 64-bit binaries for Windows platform. So, now JxBrowser provides both the jxbrowser-win32.jar and jxbrowser-win64.jar libraries that contain Chromium 32-bit and Chromium 64-bit binaries accordingly. Read more.

If you use Maven, then please check the updated installation instruction.

Important: Chromium 64-bit binaries for Windows supports only Windows 64-bit environment and cannot be used on Windows 32-bit.

Java 10 + HiDPI on Windows

In JxBrowser 6.19 the limited support of Java 10 has been added. In this version we added support of HiDPI displays on Windows platform for Java 10.

Improvements and fixes:

• The Swiftshader DLLs are included into the Chromium binaries for Windows. It allows running Chromium in the environments without physical GPU, e.g. Windows Virtual Machines.
• The JSValue.toString() method has been overriden.
• The jxbrowser.threads.configureContextClassLoader System Property support has been added. It allows enabling functionality that passes the thread context class loader to each internal thread used inside the library. By default, this option is disabled.
• The issue when selecting a client SSL certificate leads to the web page loading failure with the ERR_SSL_CLIENT_AUTH_CERT_NO_PRIVATE_KEY error code has been fixed.
• The issue when printing sometimes cannot be completed on Windows platform has been fixed.
• The issue with broken scaling in JavaFX has been fixed. It happened when BrowserView is embedded into JFXPanel in the HEAVYWEIGHT rendering mode and DPI has been changed.
• The issue when calling JSObject.getProperty() in a popup window can lead to NullPointerException in Swing applications has been fixed.
• The issue with a single pixel white line at right and bottom of a Java frame running in the fullscreen mode on Linux.

Request evaluation licence
Download JxBrowser 6.21

Release date: June 22, 2018

It's already available in the Maven repository. Please don't forget to check the updated installation instruction.

You can call the com.teamdev.jxbrowser.chromium.internal.ChromiumBuild.version() method. It returns a string that represents the Chromium build number used in this JxBrowser version (e.g. "64.0.3282.24").

No, the build number is hard-coded in the source code. So, you can get the build number only at runtime.

Malcolm, I don't see any reports from you regarding these changes with Browser popups. Could you please submit a support request with more details on what's went wrong with 6.21 in your case?