[badging] rename idlharness.any.js to idlharness.https.any.js #21777
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
There are no reviewers for this pull request. Please reach out on W3C's irc server (irc.w3.org, port 6665) on channel #testing (web client) to get help with this. Thank you! |
`[SecureContext]` is used so the API is only available over HTTPS.
foolip
force-pushed
the
foolip/badging-https
branch
from
5512843
to
b1585dd
Compare
stephenmcgruer
approved these changes
Feb 13, 2020
|
The ideal thing would be to run tests in both secure and non-secure contexts and assert the absence of the APIs when they should be absent. But that's very much a nice-to-have, as it is the rule of thumb is that if anything under test is |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
[SecureContext]is used so the API is only available over HTTPS.