diff --git a/source b/source index 301c81f996d..7f09054383a 100644 --- a/source +++ b/source @@ -79986,8 +79986,8 @@ interface BarProp {
same-origin
"This behaves the same as "same-origin-allow-popups
", with the addition any
- auxiliary browsing context created needs to contain same origin
+ data-x="coop-same-origin-allow-popups">same-origin-allow-popups", with the addition that
+ any auxiliary browsing context created needs to contain same origin
documents that also have the same cross-origin opener policy or it will appear
closed to the opener.
Return false.
Cross-Origin-Opener-Policy
`
+ headerA 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:Document
's cross-origin opener
policy is derived from the `BarProp {
Let activeDocumentNavigationOrigin be browsingContext's active
@@ -80186,7 +80187,8 @@ interface BarProp {
href="https://github.com/whatwg/html/issues/5350">whatwg/html issue #5350 for defining
browsing session. It is roughly analogous to a top-level browsing
context except that it cannot be replaced due to a `Cross-Origin-Opener-Policy
` header or navigation.
A top-level browsing context has an associated browsing session which is a @@ -82000,7 +82002,8 @@ interface Location { // but see also url, finalSandboxFlags, incumbentNavigationOrigin, and activeDocumentNavigationOrigin.
Let responseCOOP be "unsafe-none
".
Let responseCOOP be "unsafe-none
".
Let browsingContextSwitchNeeded be false.
Let responseCOOP be "unsafe-none
".
While true:
@@ -82234,7 +82238,7 @@ interface Location { // but see also obtaining a @@ -82243,17 +82247,17 @@ interface Location { // but see also unsafe-none", then set response to an - appropriate network error and return. + data-x="coop-unsafe-none">unsafe-none", then set response to an + appropriate network error and break. -This results in a network error as one cannot simultaneously provide a - clean slate to a response using cross-origin opener policy and sandbox the result of +
This results in a network error as one cannot simultaneously provide a + clean slate to a response using cross-origin opener policy and sandbox the result of navigating to that response.
Let responseRequiresBrowsingContexGroupSwitch be the result of checking if the response requires a - browsing context group switch given browsingContext, + data-x="check-browsing-context-group-switch-response">checking if the response requires a + browsing context group switch given browsingContext, responseOrigin, and responseCOOP.
If responseRequiresBrowsingContextGroupSwitch is true, set @@ -82272,8 +82276,6 @@ interface Location { // but see also mailto: URLs and such.
If response is a network error, then break.