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
Make it possible to choose Geckodriver for Firefox #2600
Comments
+1 with this feature. On Node I managed to get around this by manipulating the path on |
Is there a way of using the Firefox ServiceBuilder when creating a driver via a Builder? For Chrome I use setDefaultService, but there's no equivalent for Firefox. |
There is a somewhat detailed description of the underlying problem and grunt based solution here: |
Meta -
OS: OS X
Selenium Version: v3.0.0-beta-2
Browser: Firefox 48
Javascript/NodeJS version
In the current version the Geckodriver is found searching the PATH. I would love to see the same implementation as for Chrome and Chromedriver where you can specify the Chromedriver using the ServiceBuilder. Or a simpler solution for now where you can specify the path to Geckodriver using a property.
That would make it easier for us to automatically choose which Geckodriver to use, so the user doesn't need to be involved (in an embedded app).
The text was updated successfully, but these errors were encountered: