Skip to content

Commit

Permalink
[e] (0) The platform is full of crazy.
Browse files Browse the repository at this point in the history
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=12502

git-svn-id: http://svn.whatwg.org/webapps@6153 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed May 27, 2011
1 parent 4690d9a commit 822491d
Show file tree
Hide file tree
Showing 3 changed files with 27 additions and 18 deletions.
15 changes: 9 additions & 6 deletions complete.html
Expand Up @@ -60429,13 +60429,16 @@ <h3 id=windows><span class=secno>6.1 </span>Browsing contexts</h3>
<code><a href=#window>Window</a></code> object.</p>

<p class=note>In general, there is a 1-to-1 mapping from the
<code><a href=#window>Window</a></code> object to the <code><a href=#document>Document</a></code> object. In
one particular case, a <code><a href=#window>Window</a></code> can be reused for the
presentation of a second <code><a href=#document>Document</a></code> in the same
<a href=#browsing-context>browsing context</a>, such that the mapping is then
2-to-1. This occurs when a <a href=#browsing-context>browsing context</a> is <a href=#navigate title=navigate>navigated</a> from the initial
<code><a href=#window>Window</a></code> object to the <code><a href=#document>Document</a></code> object.
There are two exceptions. First, a <code><a href=#window>Window</a></code> can be reused
for the presentation of a second <code><a href=#document>Document</a></code> in the same
<a href=#browsing-context>browsing context</a>, such that the mapping is then 2-to-1.
This occurs when a <a href=#browsing-context>browsing context</a> is <a href=#navigate title=navigate>navigated</a> from the initial
<code><a href=#about:blank>about:blank</a></code> <code><a href=#document>Document</a></code> to another, with
<a href=#replacement-enabled>replacement enabled</a>.</p>
<a href=#replacement-enabled>replacement enabled</a>. Second, a <code><a href=#document>Document</a></code>
can end up being reused for several <code><a href=#window>Window</a></code> objects when
the <code title=dom-document-open><a href=#dom-document-open>document.open()</a></code> methos is
used, such that the mapping is then 1-to-many.</p>

<p class=note>A <code><a href=#document>Document</a></code> does not necessarily have a
<a href=#browsing-context>browsing context</a> associated with it. In particular,
Expand Down
15 changes: 9 additions & 6 deletions index
Expand Up @@ -60449,13 +60449,16 @@ _:n2 hcard:adr%20street-address "Avenue Q" ;
<code><a href=#window>Window</a></code> object.</p>

<p class=note>In general, there is a 1-to-1 mapping from the
<code><a href=#window>Window</a></code> object to the <code><a href=#document>Document</a></code> object. In
one particular case, a <code><a href=#window>Window</a></code> can be reused for the
presentation of a second <code><a href=#document>Document</a></code> in the same
<a href=#browsing-context>browsing context</a>, such that the mapping is then
2-to-1. This occurs when a <a href=#browsing-context>browsing context</a> is <a href=#navigate title=navigate>navigated</a> from the initial
<code><a href=#window>Window</a></code> object to the <code><a href=#document>Document</a></code> object.
There are two exceptions. First, a <code><a href=#window>Window</a></code> can be reused
for the presentation of a second <code><a href=#document>Document</a></code> in the same
<a href=#browsing-context>browsing context</a>, such that the mapping is then 2-to-1.
This occurs when a <a href=#browsing-context>browsing context</a> is <a href=#navigate title=navigate>navigated</a> from the initial
<code><a href=#about:blank>about:blank</a></code> <code><a href=#document>Document</a></code> to another, with
<a href=#replacement-enabled>replacement enabled</a>.</p>
<a href=#replacement-enabled>replacement enabled</a>. Second, a <code><a href=#document>Document</a></code>
can end up being reused for several <code><a href=#window>Window</a></code> objects when
the <code title=dom-document-open><a href=#dom-document-open>document.open()</a></code> methos is
used, such that the mapping is then 1-to-many.</p>

<p class=note>A <code><a href=#document>Document</a></code> does not necessarily have a
<a href=#browsing-context>browsing context</a> associated with it. In particular,
Expand Down
15 changes: 9 additions & 6 deletions source
Expand Up @@ -68867,14 +68867,17 @@ _:n2 hcard:adr%20street-address "Avenue Q" ;
<code>Window</code> object.</p>

<p class="note">In general, there is a 1-to-1 mapping from the
<code>Window</code> object to the <code>Document</code> object. In
one particular case, a <code>Window</code> can be reused for the
presentation of a second <code>Document</code> in the same
<span>browsing context</span>, such that the mapping is then
2-to-1. This occurs when a <span>browsing context</span> is <span
<code>Window</code> object to the <code>Document</code> object.
There are two exceptions. First, a <code>Window</code> can be reused
for the presentation of a second <code>Document</code> in the same
<span>browsing context</span>, such that the mapping is then 2-to-1.
This occurs when a <span>browsing context</span> is <span
title="navigate">navigated</span> from the initial
<code>about:blank</code> <code>Document</code> to another, with
<span>replacement enabled</span>.</p>
<span>replacement enabled</span>. Second, a <code>Document</code>
can end up being reused for several <code>Window</code> objects when
the <code title="dom-document-open">document.open()</code> methos is
used, such that the mapping is then 1-to-many.</p>

<p class="note">A <code>Document</code> does not necessarily have a
<span>browsing context</span> associated with it. In particular,
Expand Down

0 comments on commit 822491d

Please sign in to comment.