Skip to content

Commit e991e2f

Browse files
zcorpandomenic
authored andcommitted
Remove user override of window.open() in a sandbox
Fixes #5806. Test: web-platform-tests/wpt#24974
1 parent 21da9f8 commit e991e2f

File tree

1 file changed

+1
-17
lines changed

1 file changed

+1
-17
lines changed

source

Lines changed: 1 addition & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -77811,23 +77811,7 @@ console.assert(iframeWindow.frameElement === null);
7781177811
<dt id="sandboxWindowOpen">If <var>sandboxingFlagSet</var> has the <span>sandboxed auxiliary
7781277812
navigation browsing context flag</span> set</dt>
7781377813

77814-
<dd>
77815-
<p>The user agent may offer the user one of:
77816-
77817-
<ol>
77818-
<li><p>Set <var>chosen</var> to the result of <span>creating a new top-level browsing
77819-
context</span> and set <var>windowType</var> to "<code data-x="">new and
77820-
unrestricted</code>".</p></li>
77821-
77822-
<li><p>Set <var>chosen</var> to an existing <span>top-level browsing context</span>.</p>
77823-
</ol>
77824-
77825-
<p class="warning">If this case occurs, it means that an author has explicitly sandboxed the
77826-
document that is trying to open a link.</p>
77827-
77828-
<p class="note">If the user declines or the user agent doesn't offer the above, the variables
77829-
remain unchanged.</p>
77830-
</dd>
77814+
<dd><p>The user agent may report to a developer console that a popup has been blocked.</p></dd>
7783177815

7783277816
<dt>If the user agent has been configured such that in this instance it will create a new
7783377817
browsing context</dt>

0 commit comments

Comments
 (0)