Skip to content
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

Chrome 111 is failing due to a missing argument. #40

Closed
jason-edstrom opened this issue Apr 14, 2023 · 0 comments · Fixed by #42
Closed

Chrome 111 is failing due to a missing argument. #40

jason-edstrom opened this issue Apr 14, 2023 · 0 comments · Fixed by #42
Labels
bug Something isn't working

Comments

@jason-edstrom
Copy link
Contributor

There is an issue with the HTTP client for Chrome 111 (and by extension, Edge) that causes test runs to fail without the --remote-allow-origins=* argument added.

See: SeleniumHQ/selenium#11750
@jason-edstrom jason-edstrom added the bug Something isn't working label Apr 14, 2023
@jason-edstrom jason-edstrom mentioned this issue Apr 14, 2023
Open
jason-edstrom added a commit that referenced this issue Apr 14, 2023
@jason-edstrom
openmaqs-java #40 Added workaround argument as a default. Re-enable E…
bd403f8 
…dge unit test thanks for Chrome-based Edge on ubuntu.
@jason-edstrom jason-edstrom linked a pull request Apr 14, 2023 that will close this issue
#40 - Fix for Chrome based browsers version 111 #42
Merged
jason-edstrom added a commit that referenced this issue Apr 14, 2023
@jason-edstrom
#40 - Fix for Chrome based browsers version 111 (#42)
a5a1233
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

#40 - Fix for Chrome based browsers version 111 OpenMAQS/openmaqs-java
1 participant
@jason-edstrom