-
Notifications
You must be signed in to change notification settings - Fork 103
'acceptInsecureCerts' Argument for Start-SeFirefox? #189
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
Comments
As far as I know, it is not possible with V3. In V4, you'd start the browser in the following manner:
At that point though, you would get the certificate error. Here is the relevant code.
Note that while testing this, I found an issue (#191) that will prevent this from working in V4.0-preview1. V4 is a major rewrite from V3 though and if you had working V3 scripts, there will definitely be rework to make them V4 compliant. |
I'll keep this issue open until V4.0.0-Preview2 is released |
It looks like at least Chrome support that too.
The |
Done. In v4.0-preview2, you'll be able to use :
I'll publish a release by Dec. 7th end of day. |
* Start-SeEdgeDriver throw error on launch (#188) * Edge fix + general debug fix * .Where is not a method for CIM Instance object (#190) * Firefox not using the proper DriverOption (#191) * Filter parameter to get-seelement and applied to Get-SeInput (#186 #192 ) Also fixed a logic error with $Value that was used both as a parameter and a variable, which caused issues. * Legacy code removal causing error with screenshots (#187) * Fix - Filter + Filter error message * Select input by attributes fix. * Edge (new) driver option need to be of type ChromeOptions (#195) * Edge driver option fix (#193) * Edge - semi revert (#197) Since Start-SeDriver have priority over options, options should not handle stuff that depends on parameters. * IE fix (#193) * MSEdge Fix (#193) * ErrorAction Stop when MSEdge Service fail to create. * AcceptInsecureCertificates (Firefox, Chrome, Edge) (#189) * #177 Get-SeInput view (initial commit) * V4.0.0-preview2 build * Drivers update * V4.0.0-preview2 changelog * Version update
Is this an available option?
The text was updated successfully, but these errors were encountered: