-
-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[🐛 Bug]: The page load ime setting is not respected #13251
Comments
@KarelHaruda, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
There are a number of different timeout values that can be set and it isn't obvious how they work together. In this case, |
ClientConfig.defaultConfig().readTimeout solved the problem. Thank you very much |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What happened?
I'm trying to set the Page Load timeout to 120 min, but I always get a Timeout Exception after about 3 minutes.
At the same time, all times are set to 120 min, as can be seen in the Relevant log output.
At first I tried only pageLoad timeout and finally all timeouts
timeouts: {implicit: 7200000, pageLoad: 7200000, script: 7200000}
How can we reproduce the issue?
Relevant log output
Operating System
Windows 11, Linux
Selenium version
4.15.0
What are the browser(s) and version(s) where you see this issue?
117.0.5938.150
What are the browser driver(s) and version(s) where you see this issue?
117.0.5938.149
Are you using Selenium Grid?
No response
The text was updated successfully, but these errors were encountered: