joerg1985

Use of guava in `org.openqa.selenium.support.ui.FluentWait` has been removed.

@titusfortner still waiting for the review of #13308 by @shs96c After the PR the is merged there is only one use of guava left (the breaking change in `org.openqa.selenium.support.ui.ExpectedCondition`).

@diemol @titusfortner Now is only one use of guava left is the breaking change in `org.openqa.selenium.support.ui.ExpectedCondition` would be greate to have this completed in `4.19.0`.

No, i did not know how to proper document this breaking change in the release notes. It is just removing the guava interface from the selenium interface and remove the...

@diemol yes this is still open, as it is in milestone selenium 5.0. I think this could be implemented earlier, but there is a risk for e.g. appium to run...

I just have pushed a commit cdbe9c627296eee222c64c4deca58ffa25610664 that might point into the direction why there are idling websocket. There was a misunderstanding in what cases the `onError` is called in...

@bhecquet the reference to the HttpClient should be dropped after some time, so this list should not be an issue. Could you retest with selenium 4.16.0?

Okay one thing that should be checked, we have chain like this: `Client Grid Node Driver` Now the Driver does raise an error on the Websocket `Client Grid Node *...

Running the code of #13316 in a loop does leak threads for me and also log's warnings: ``` 11:20:32.724 WARN [DefaultChannelPipeline.onUnhandledInboundException] - An exceptionCaught() event was fired, and it reached...

This should be the one for the `CdpEndpointFinder` to get the websocket url of the DevTools, before the driver is created.