-
Notifications
You must be signed in to change notification settings - Fork 68
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
Error: chrome.setDefaultService is not a function #538
Comments
Just for future reference, I was able to work around this issue by adding this on the RUN cd $(npm list -g | head -n 1)/node_modules/@axe-core/cli && npm install selenium-webdriver@4.3.0 --save-exact |
Hey @renato-bohler, I saw that selenium webdriver did infact create a breaking change when upgrading from version 4.3.0 -> 4.3.1 by removing that function. I should have a PR here shortly to pin to use selenium webdriver 4.3.0 |
I came across the same issue. The PR leading to this is SeleniumHQ/selenium#10796 |
Validated with |
Closing no docs required |
The following error started to happen on my project's pipeline today when running axe CLI:
After a little bit of investigation, I've found out that the culprit is apparently version
4.3.1
ofselenium-webdriver
(published ~3 hours ago). The previous version (4.3.0
) does contain thesetDefaultService
function:But the new one (
4.3.1
) does not:If that's not a bug on their side, this should be published as a breaking change (
5.0.0
), but in the meantime, using version4.3.0 (exact)
is probably going to fix this issue on axe's side.The text was updated successfully, but these errors were encountered: