From b2121238b74b5ac4971cbd390501412007c915d8 Mon Sep 17 00:00:00 2001 From: "Michael[tm] Smith" Date: Sun, 6 Nov 2016 19:39:31 +0900 Subject: [PATCH] Clarify rel=noopener & "disown opener" effects --- source | 20 +++++++++++++++++--- 1 file changed, 17 insertions(+), 3 deletions(-) diff --git a/source b/source index 2fd27210f3d..f0c4541b560 100644 --- a/source +++ b/source @@ -22861,7 +22861,7 @@ interface HTMLHyperlinkElementUtils { not allowed Annotation · - Requires that any browsing context created by following the hyperlink must not have an opener browsing context. + Requires any browsing context created by following the hyperlink to disown its opener. @@ -23444,8 +23444,8 @@ interface HTMLHyperlinkElementUtils { implied hyperlink, if no other keywords create one).

The keyword indicates that any newly created browsing context which results from - following the hyperlink will not have an opener browsing context, which - means that its window.opener property will be hyperlink will have disowned its opener, which means that + its window.opener property will be null.

Link type "pingback"
@@ -76994,6 +76994,20 @@ console.assert(iframeWindow.frameElement === null); where value is the new value.

+
+

If a browsing context has disowned its + opener, the value of its window.opener is null. That prevents scripts in the browsing context from changing + any properties of its opener browsing context's Window (i.e., the window + from which the browsing context was created).

+ +

Otherwise, if a browsing context has not disowned its + opener, then scripts in that browsing context can use window.opener to change properties of its opener browsing + context's Window. For example, a script running in the browsing + context can change the value of window.opener.location, causing the + opener browsing context to navigate to a completely different document.

+