JxBrowser 6.13 includes several new features such as functionality that allows programmatically triggering DOM events and configuring WebRTC IP handling policy. We also keep improving the library by implementing fixes requested by the users.
Creating and dispatching DOM events
In this version JxBrowser DOM Events API is extended with new methods and classes, which allow creating and triggering DOM events at the specified HTML element. Starting from v6.13 JxBrowser supports the Event, UIEvent, MouseEvent, and KeyEvent DOM events. To dispatch an event use the DOMEventTarget.dispatchEvent(DOMEvent event) method.
WebRTC IP handling policy
The BrowserPreferences class is extended with the setWebRTCIPHandlingPolicy(WebRTCIPHandlingPolicy policy) method that allows configuring WebRTC IP handling policy. The list of supported policies is available in the WebRTCIPHandlingPolicy enum.
No pain with OS detection in old JREs
The environment validation algorithm is improved. JxBrowser detects OS name and version using standard Java system properties such as “os.name” and “os.version”. Old JREs such as 1.6 don’t recognize modern operating systems and detect them as “Windows NT (unknown)” which leads to the “com.teamdev.jxbrowser.chromium.internal.EnvironmentException: Unsupported operating system. Supported OS: Windows 7, 8, 10, Windows Server 2008 R2, 2012, 2016, macOS 10.9+ & Linux. Current OS: Windows NT (unknown), version: 6.2” exception. The workaround was to manually set “os.name” to a string that contains supported operating system name such as “Windows 7” or “Windows Server 2016”. This workaround wasn’t convenient for JxBrowser customers.
In this update we made environment validation less strong. Now, JxBrowser checks only minimal supported OS and JRE version. It allows using the library with old JREs such as 1.6 on modern operating systems such as Windows Server 2016 without any workarounds or manipulations with the “os.name” system properties.
The following functionality got better in v6.13:
Here’s what has been resolved in this update:
Release date: February 28, 2017