joerg1985

As mentioned in #12975, it might be good to have a default value which will not conflict with the default w3c page load timeout of 300s. Otherwise there are situations...

@titusfortner i was not sure if there where more/higher w3c timeouts, but it seems like the page load is the highest one: - Script timeout 30,000 ms - Page load...

Okay, this will be a breaking change: https://github.com/SeleniumHQ/selenium/blob/e5182732e95bddbaf91a042c6a70bacf20a5ac85/java/src/org/openqa/selenium/support/ui/ExpectedCondition.java#L34-L36

It should be working fine with the native java interface.

I just pushed a commit (42cc35585b8a60f722c67d34fdc877e3b4c2c89b) to remove the usage of guava from the browser bindings. These are left areas are left: - devtools -> #12943 - bidi -> same...

Yes i have planned to work on this as soon as possible. I think i will continue after christmas. I will split this in multiple tasks the next days.

Okay, i had a look and there is not much left, but there is one question how to remove the use of `com.google.common.net.HttpHeaders` and `com.google.common.net.MediaType` before i could split the...

I just created the `less-guava` branch which removes all easy to replace guava uses. I would merge this to main, after the release of 4.16.0, if the new class `org.openqa.selenium.remote.http.HttpHeader`...

@diemol @titusfortner i have just pushed a commit to replace most of the usages, these tasks are left: - update `org.openqa.selenium.support.ui.ExpectedCondition`, this is a breaking change so i did not...

Ok i was not able to describe all changes to remove the `FileBackedOutputStream` and `CountingOutputStream`, as this is not that trivial and i had to check a lot of things...