[🚀 Feature]: Implement `ClientConfig` in .NET/Ruby/JavaScript

[p0deje]

In Java and Python, there is a ClientConfig class that is responsible for configuring client-specific options that are not applicable to the remote, such as HTTP connection timeouts. Now that we want to add WebSocket timeout options, it makes sense to unify this across the bindings and provide a similar API to set these timeouts and allow passing them to the WebDriver constructor.

Reference:

• https://github.com/SeleniumHQ/selenium/blob/2280161d4fc70da9294f496e15d990f643721311/java/src/org/openqa/selenium/remote/http/ClientConfig.java
• https://github.com/SeleniumHQ/selenium/blob/b3fc1b348e16e4d8afc090bc44f5fff18ed5114a/py/selenium/webdriver/remote/client_config.py

Related to #16053.

[selenium-ci]

@p0deje, thank you for creating this issue. We will troubleshoot it as soon as we can.

Selenium Triage Team: remember to follow the Triage Guide

[nvborisenko]

It looks like abstraction layer over native implementation. And in my really honest opinion it is unnecessary. In .NET usually it is achieved via factory, where user is able to set everything he wants. See:

var driver = new ChromeDriver(new ChromeOptions()
{
  ConfigureHttpClientHandler = client => client.Timeout = TimeSpan.FromSeconds(5)
})

Dummy code, just to highlight idea. This is:

• Simple: really what I wrote will work
• Powerful: we expose everything, so user can do everything! Even bypass proxy for localhost: [🚀 Feature]: Allow setting the proxy/HttpClientHandler for DriverService #15954
• Microsoft maintainable: Implement once and forget.

I really cannot recall where I have faced unnecessary abstraction layer for HTTP Config, nowhere.

About unifying WebSocket and HttpClientHandler options... for me it is unification of cat and dog. Wrong way in my opinion.

[p0deje]

I'm fine with the .NET bindings providing a language-specific implementation that fits best in its world. The key here is to have a way to override default WebSocket timeouts, given those exist in the WebSocket client .NET implementation.

[nvborisenko]

Since you accepted my proposal, let's think further. My proposal is about to expose native http/websocket options via a function, which user can define to configure options, absolutely all available options in the underlying implementation, not only wrapped by selenium. And it is not only about .NET.

[cgoldberg]

provide a similar API to set these timeouts and allow passing them to the WebDriver constructor

FWIW, Python currently only allows the client_config to be passed to the constructor for webdriver.Remote (not any local webdrivers). You can access it through a property of the driver after you instantiate it, but it's pretty awkward. We should revisit a way to make it easier to create any driver using an existing ClientConfig.

Edit: I just created #16282 to track this for Python