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.

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

Closed
renato-bohler opened this issue Jul 7, 2022 · 5 comments
Closed

Error: chrome.setDefaultService is not a function #538

renato-bohler opened this issue Jul 7, 2022 · 5 comments

Comments

@renato-bohler
Copy link

The following error started to happen on my project's pipeline today when running axe CLI:

image

After a little bit of investigation, I've found out that the culprit is apparently version 4.3.1 of selenium-webdriver (published ~3 hours ago). The previous version (4.3.0) does contain the setDefaultService function:

image

But the new one (4.3.1) does not:

image

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 version 4.3.0 (exact) is probably going to fix this issue on axe's side.


axe-core version: 4.4.2
@axe-core/4.4.3

- Node version: v17.9.0
- Platform:  Linux
@renato-bohler
Copy link
Author

renato-bohler commented Jul 7, 2022

Just for future reference, I was able to work around this issue by adding this on the Dockerfile we're using, after installing @axe-core/cli globally:

RUN cd $(npm list -g | head -n 1)/node_modules/@axe-core/cli && npm install selenium-webdriver@4.3.0 --save-exact

@michael-siek
Copy link
Member

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

@MarkusJLechner
Copy link

I came across the same issue. The PR leading to this is SeleniumHQ/selenium#10796

@padmavemulapati
Copy link

Validated with axe-core-npm@4.4.4-alpha.299 version, selenium-webdriver@4.3.0 and chrome driver(104.0.0), not seeing any error.

@michael-siek
Copy link
Member

Closing no docs required

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants