Releases · seleniumhq-community/htmlunit-remote

The Selenium project moved the WebDriverInfo interface from the org.openqa.selenium package to org.openqa.selenium.remote. I had updated the relevant import statement, but I forgot to rename the associated SPI declaration file. As a consequence, Selenium Grid was unable to locate HtmlUnitDriverInfo, which caused HtmlUnit nodes to abort on launch.

This release resolve the issue by updating the name of the WebDriverInfo SPI declaration file.

Assets 2

20 Jan 21:32

sbabcoc

htmlunit-remote-4.40.0

dafda8b

Upgrade to version 4.40.0; update stale POM SCM values; fix inaccurate import

This release is primarily focused on upgrading Selenium/HtmlUnit to version 4.40.0.

In the process, I stumbled over a couple of issues:

The <scm> node of the POM specified stale URLs that pointed to the former home of this project.
The HtmlUnitDriverInfo class specified an improper import for the WebDriverInfo interface.

For some reason, my old machine was able to work as expected with these issues. My new machine isn't so forgiving.

Assets 2

07 Dec 21:48

sbabcoc

htmlunit-remote-4.39.0

8db17c2

Upgrade to version 4.39.0; fix [browserVersion] issue

In this release, we upgraded to the latest releases of Selenium and HtmlUnitDriver (version 4.39.0).

We also fixed an issue that caused Selenium Grid slot match failures on driver requests that specify the browserVersion capability. The solution was to add a new vendor-specific capability: garg:browserVersion. This capability is ignored by the Grid distributor for slot matching, allowing proper matching and configuration of HtmlUnitDriver nodes.

Assets 2