This repository has been archived by the owner on Mar 14, 2024. It is now read-only.
Correct description of COOP unsafe-none
#3185
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
Contrary to the current explanation, when an opener specifies a COOP of `same-origin-allow-popups` and the opened resource specifies `unsafe-none`, then the two documents *will* share the same browsing context group. This is supported by the explanation of `same-origin-allow-popups` which precedes this section: > A top-level document with `same-origin-allow-popups` retains references to > any of its popups which either don't set COOP or which opt out of isolation > by setting a COOP of `unsafe-none`. It is also supported by the proposed specification text [1] which reads: > To check if a response requires a browsing context group switch , > given a browsing context browsingContext , an origin responseOrigin > and a cross-origin opener policy responseCOOP , run the followign > steps: > > [...] > > 6. If all of the following are true: > > - isInitialAboutBlank > - activeDocumentCOOP is " same-origin-allow-popups ". > - responseCOOP is " unsafe-none ". > > then return false. Update the explanation to only include the relevant condition (that is: a COOP of `same-origin`). [1] whatwg/html#5334
|
Deploy preview for web-dev-staging ready! Built with commit c9106e5 |
domenic
approved these changes
Jun 10, 2020
kaycebasques
approved these changes
Jun 10, 2020
kaycebasques
added
content update
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Contrary to the current explanation, when an opener specifies a COOP of
same-origin-allow-popupsand the opened resource specifiesunsafe-none, then the two documents will share the same browsingcontext group.
This is supported by the explanation of
same-origin-allow-popupswhichprecedes this section:
It is also supported by the proposed specification text [1] which reads:
Update the explanation to only include the relevant condition (that is:
a COOP of
same-origin).[1] whatwg/html#5334
Fixes #SOME_ISSUE_NUMBER
Changes proposed in this pull request: