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
Fix ChromeDriver acceptInsecureCerts capability tests #19584
Conversation
PR web-platform-tests#19402 added acceptInsecureCerts capability to Chrome configuration by default. This causes failures in tests that explicitly check this capability. Fixing by removing the default acceptInsecureCerts capability during new_session tests.
@Hexcles PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like Firefox always adds acceptInsecureCerts
. I'm wondering why the problem only arose after #19402 .
For Firefox, https://github.com/web-platform-tests/wpt/blob/master/tools/wptrunner/wptrunner/browsers/firefox.py#L132 add |
We don’t use the browser initialisation code referenced in https://github.com/web-platform-tests/wpt/blob/master/tools/wptrunner/wptrunner/browsers/firefox.py#L132 for the wdspec type. In the wdspec case we rely entirely on what the WebDriver implementation does by default. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change is fine though, it doesn’t affect geckodriver at all and solves the chromedriver case.
Do note that chromedriver should not default to have acceptInsecureCerts
on by default, so maybe this should be considered a chromedriver bug?
That was the case (https://crbug.com/chromedriver/3148), and it's been fixed, which is why I needed to change wptrunner to explicitly ignore cert errors in Chrome, but the change inadvertently affected wdspec tests. And thanks for the explanation! |
Taskcluster detected a slow test on Firefox: It's definitely unrelated to this change so I'm going to admin-merge it. |
Ah, thanks for the explanation! |
PR #19402 added acceptInsecureCerts capability to Chrome configuration
by default. This causes failures in tests that explicitly check this
capability. Fixing by removing the default acceptInsecureCerts
capability during new_session tests.