COEP requires a secure context #22929
Merged
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
wpt-pr-bot
requested review from
arturjanc,
domenic,
foolip,
hemeryar,
jdm,
jgraham,
jugglinmike,
mikewest,
valenting,
zcorpan and
zqzhang
|
Just to make sure, what's the reasoning of restricting COEP to secure contexts? Restricting crossOriginIsolated to secure contexts makes sense, but COEP itself is a restricting feature so enabling COEP on non-secure contexts wouldn't be harmful, I think. |
yutakahirano
approved these changes
Apr 15, 2020
|
I see, thanks. IIUC this is not specced, so can you file a spec bug and assign me to it? |
|
@yutakahirano sure, whatwg/html#4930. |
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.
Neither Chrome nor Firefox seem to currently require this, so let's add a test...