-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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]: Setting lang attribute doesn't apply to the test containers #1750
Comments
Looks like this still doesn't work.... ChromeOptions set:
And the lang attribute is send in the prefs when node container is created:
I wanted to check before I submit a new PR. Should I set the env variable in the wrapper script instead of outside? It looks like it's setting the LANGUAGE env variable but in the "default" node container, not the dynamically generated actual node containers for test runs? I can see when starting a bash session inside the test container, the env variable of "LANGUAGE" is still set to en-US:
Perhaps we should set the env variable in the script passed to the container to start the chrome executable? |
Something like:
|
(@diemol I can't reopen this issue) |
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?
When trying to run with a different locale, trying all possible ways to set this via the chromedriver doesn't seem to work.
Apparently there is an issue with setting this, and needs to be done at the env variable level. This was previously identified:
elgalu/docker-selenium#159
And I am still seeing the same behaviour in the current docker selenium images.
Command used to start Selenium Grid with Docker
Relevant log output
Operating System
Centos 9
Docker Selenium version (tag)
4.5.0
The text was updated successfully, but these errors were encountered: