This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24733 - Nested browsing contexts shouldn't be script-closable
Summary: Nested browsing contexts shouldn't be script-closable
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-19 23:28 UTC by Leif Kornstaedt
Modified: 2016-04-27 00:51 UTC (History)
4 users (show)

See Also:

Attachments

Description Leif Kornstaedt 2014-02-19 23:28:35 UTC 
"A browsing context is script-closable if it is an auxiliary
  browsing context that was created by a script (as opposed to by an action of the user), or
  if it is a browsing context whose session history contains only one
  Document."

Should the text after the "or" read: "if it is a *top-level* browsing context whose ..."?  Or is this implied by another condition that I'm missing?
Comment 1 Travis Leithead [MSFT] 2016-04-27 00:51:44 UTC 
HTML5.1 Bugzilla Bug Triage: This has been fixed in a prior integration of content from the WHATWG spec. Now includes the term "top level" as suggested.

If this resolution is not satisfactory, please copy the relevant bug details/proposal into a new issue at the W3C HTML5 Issue tracker: https://github.com/w3c/html/issues/new where it will be re-triaged. Thanks!