Scott Babcock

@diemol It seems like you're advocating for ignoring all extension capabilities for purposes of slot matching. This approach would mean that custom matchers would be required in all scenarios where...

@diemol I can revise my PR to implement this strategy. It is significantly less complex to implement and much easier to describe. I'll update the unit tests accordingly. Is the...

@diemol Yes, but you can only specify one custom matcher. If you need sessions from multiple vendors, this means running with multiple hubs. With a slot matcher extension mechanism, vendor-specific...

The `codiumai-pr-agent-pro` suggestions are all entirely off the mark.

I think you'll notice a pronounced performance improvement by using the **Capabilities** API instead of copying all of the **WebClientOptions** properties en masse with the `importOptions` method.

@rbri Absolutely! Were those unit tests running faster with these revisions? Also, do you have a timeline for releasing **HtmlUnit** 4.4.0 with that hidden element fix?

We apparently also need an **HtmlUnitDriverService**, which extends **org.openqa.selenium.remote.service.DriverService**. This may be the more involved task, because it seems to require packaging up **HtmlUnitDriver** into a service that can launch...

I abandoned my attempt to stand up a Grid 4 node that provides HtmlUnit sessions. I need to examine the `InMemorySession` feature of Selenium 3 to determine the size and...

I've created the [HtmlUnit Remote](https://github.com/sbabcoc/htmlUnit-remote) project to resolve this issue.

The wrinkle here is that we now have Appium extension capabilities which are being matched through this improper behavior. Fixing this is going to require either adding explicit matching for...