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 10092 - "The transitive closure of all the browsing contexts that are directly reachable browsing contexts forms a unit of related browsing contexts." Since a browsing context is not a directly reachable browsing context of itself, this means that top-level brow
Summary: "The transitive closure of all the browsing contexts that are directly reacha...
Status: CLOSED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-05 21:17 UTC by contributor
Modified: 2010-10-04 13:58 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-07-05 21:17:58 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#groupings-of-browsing-contexts

Comment:
"The transitive closure of all the browsing contexts that are directly
reachable browsing contexts forms a unit of related browsing contexts."  Since
a browsing context is not a directly reachable browsing context of itself,
this means that top-level browsing contexts with no children, opener, or
opened contexts will not be part of any unit of related browsing contexts.  Is
this intended?

Posted from: 68.175.61.233
Comment 1 Ian 'Hixie' Hickson 2010-08-30 17:48:14 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: see diff given below
Rationale: It is not.
Comment 2 contributor 2010-08-30 17:50:51 UTC 
Checked in as WHATWG revision r5394.
Check-in comment: Make sure single top-level BCs still get an event loop.
http://html5.org/tools/web-apps-tracker?from=5393&to=5394