New presentation start tests that trigger a mixed content error #3590
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The tests need to run over HTTPS, hence the
.https.html
extension. They create aPresentationRequest
with an HTTP URL and ensure thatstart
reports aSecurityError
exception.Note the tests will pass if they are run over HTTP by mistake (since there would not be any "mixed content" anymore), which could be confusing. A short exchange on IRC suggested that individual test files should not check the protocol themselves, but that the test harness could perhaps be updated to report the error. I prepared a PR on testharness.js accordingly: w3c/testharness.js#207