[🐛 Bug]: DevTools timeout is hardcoded and not sufficient for some commands

[dennisoelkers]

What happened?

(If this is a bug or a feature is certainly discussable. I decided to file it as a bug, because it is effectively blocking functionality in our code that should work without having to add a feature)

The timeout used for executing DevTools commands in the Java library is hardcoded to 10 seconds. For some commands (e.g. printing a large/complex page to PDF) or on overloaded systems, this might not be enough. It should be configurable.

How can we reproduce the issue?

-

Relevant log output

-

Operating System

Linux

Selenium version

Java 4.22.0

What are the browser(s) and version(s) where you see this issue?

Chrome 124

What are the browser driver(s) and version(s) where you see this issue?

ChromeDriver 124.0.6367.201

Are you using Selenium Grid?

No response

[github-actions]

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

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[navin772]

Hi @dennisoelkers, thanks for reporting this issue. I think this is a valid request, I will make the required changes and open a PR!