You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Selenium project's implementation of FirefoxOptions
disallows setting both prefs and profile, but the documentation here makes no reference to this limitation.
Is Selenium protecting against something that is not a problem, or should the documentation here be updated to reflect this limitation?
The text was updated successfully, but these errors were encountered:
* Fixes to FirefoxOptions.java
- Remove unneeded check for both prefs and profile being present:
According to mozilla/geckodriver#421
having both is valid.
- Add getProfile method:
Allows for use in intermediate nodes that need to modify the profile
e.g. to add additional certs or extensions.
* Fix type error.
This issue has been automatically locked since there has not been any recent activity after it was closed. If you have run into an issue you think is related, please open a new issue.
lockbot
locked and limited conversation to collaborators
Aug 17, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The Selenium project's implementation of
FirefoxOptions
disallows setting both prefs and profile, but the documentation here makes no reference to this limitation.
Is Selenium protecting against something that is not a problem, or should the documentation here be updated to reflect this limitation?
The text was updated successfully, but these errors were encountered: