From 012b7417b8fd0331711e16a8984d18fcff097ebf Mon Sep 17 00:00:00 2001 From: clamy Date: Thu, 12 Mar 2020 14:47:50 +0100 Subject: [PATCH] Addressed comments --- source | 25 ++++++++++++++++++------- 1 file changed, 18 insertions(+), 7 deletions(-) diff --git a/source b/source index 3635f566556..e7efd21b0bf 100644 --- a/source +++ b/source @@ -9375,7 +9375,7 @@ partial interface Document {

The Document has a cross-origin opener policy, which is a cross-origin opener policy, - initially "unsafe-none.

+ initially "unsafe-none".

The DocumentOrShadowRoot interface

@@ -79912,8 +79912,10 @@ console.assert(iframeWindow.frameElement === null); for collecting agent clusters when it is deemed that nothing can access them anymore.

A browsing context group has a cross-origin - isolated boolean. It is initially false. When it is true, the agent cluster map - will be keyed using origins.

+ isolated boolean. It is initially false.

+ +

The impact of cross-origin isolated is + under discussion in issue #4734.

To create a new browsing context group, run these steps:

@@ -80223,10 +80225,15 @@ console.assert(iframeWindow.frameElement === null);
  • Let currentDocument be current's active document.

  • -
  • If currentDocument's origin is not same origin - with current's top-level browsing context's - active document 's origin, then set noopener to - true.

  • +
  • +

    If currentDocument's origin is not same origin + with current's top-level browsing context's active + document 's origin, then set noopener to true and + name to "_blank".

    + +

    In the presence of COOP, nested documents cross-origin with their + top-level browsing context always set /noopener/.

    +
  • @@ -82922,6 +82929,10 @@ interface BarProp {
  • Return newBrowsingContext.

  • +

    The impact of swapping browsing context groups following a navigation is not + defined. It is currently under discussion in issue 5350.

    +

    Session history and navigation

    The session history of browsing contexts