-
-
Notifications
You must be signed in to change notification settings - Fork 8.5k
[🐛 Bug]: Chrome Driver 133.0.6943.126: Chrome's resolution is scaled by a factor of 2 #15721
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
Comments
@gamegrobla, thank you for creating this issue. We will troubleshoot it as soon as we can. Selenium Triage Team: remember to follow the Triage Guide |
Please verify that this issue still occurs with the latest version. If it no longer applies, you can close this issue or update your comment. This issue will be marked "awaiting answer" and may be closed automatically if no response is received. |
Using 4.32 version does not resolve the issue |
@gamegrobla, thank you for creating this issue. We will troubleshoot it as soon as we can. Selenium Triage Team: remember to follow the Triage Guide |
@gamegrobla the env variables should be prefixed with |
thank you for the answer, but changing those env vars doesn't fix the issue. for now I've discovered 2 ways to mitigate this issue:
|
What happens when you try this on Firefox? |
Uh oh!
There was an error while loading. Please reload this page.
Description
I am running selenium UI tests on the lates chrome driver version (133.0.6943.126) as a Docker SeleniumGrid container using TestContainers.
This is how I configure and spawn the container:
those environment variable settings proposed by Gemini don't work
here are my my chrome flags:
the problem started occuring after switching from Chrome Driver 126 (or something around it) to 133 (as mentioned before)
setting the resolution to 1080p results in a resolution of 4k (screenshots of such resolution are taken and tests that contain checking scroll-behaviour fail because there is nothing to scroll - content is displayed in the viewport at once)
currently I set the resolution to 540p to achieve 1080p - but it is a temporary solution
Reproducible Code
The text was updated successfully, but these errors were encountered: