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.

Sign up for GitHub

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

Jump to bottom

remove workaround to use chrome 111 after upgrading selenium version #1836

Closed

abendt opened this issue Apr 1, 2023 · 0 comments · Fixed by #1859

Collaborator

abendt commented Apr 1, 2023 •

edited

#1832 introduced a workaround (add --remote-allow-origins=* to ChromeOptions) to allow using Chrome 111+

After upgrading to Selenium 4.5+ this workaround should be removed and replaced with the solution here: SeleniumHQ/selenium#11750 (comment)

no replacement needed if latest Selenium version is used SeleniumHQ/selenium#11750 (comment)

depends on: #1656

The text was updated successfully, but these errors were encountered:

abendt mentioned this issue

remove selenium workaround #1859

Merged

abendt closed this as completed in #1859

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment