[html5] r5224 - [e] (0) Make some notes about the lifetime of <iframe> documents.
whatwg at whatwg.org
whatwg at whatwg.org
Thu Jul 29 17:08:06 PDT 2010
Author: ianh
Date: 2010-07-29 17:08:04 -0700 (Thu, 29 Jul 2010)
New Revision: 5224
Modified:
complete.html
index
source
Log:
[e] (0) Make some notes about the lifetime of <iframe> documents.
Modified: complete.html
===================================================================
--- complete.html 2010-07-29 23:41:49 UTC (rev 5223)
+++ complete.html 2010-07-30 00:08:04 UTC (rev 5224)
@@ -209,7 +209,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
<hgroup><h1>Web Applications 1.0</h1>
- <h2 class="no-num no-toc">Draft Standard — 29 July 2010</h2>
+ <h2 class="no-num no-toc">Draft Standard — 30 July 2010</h2>
</hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -21511,6 +21511,35 @@
<code><a href=#windowproxy>WindowProxy</a></code> object will proxy new <code><a href=#window>Window</a></code>
objects for new <code><a href=#document>Document</a></code> objects, but the <code title=attr-iframe-src><a href=#attr-iframe-src>src</a></code> attribute will not change.</p>
+ <div class=impl>
+
+ <div class=note>
+
+ <p><a href=#remove-an-element-from-a-document title="remove an element from a document">Removing</a>
+ an <code><a href=#the-iframe-element>iframe</a></code> from a <code><a href=#document>Document</a></code> does not cause
+ its <a href=#browsing-context>browsing context</a> to be discarded. Indeed, an
+ <code><a href=#the-iframe-element>iframe</a></code>'s span>browsing context can survive its
+ original parent <code><a href=#document>Document</a></code> if its <code><a href=#the-iframe-element>iframe</a></code> is
+ moved to another <code><a href=#document>Document</a></code>.</p>
+
+ <p>On the other hand, if an <code><a href=#the-iframe-element>iframe</a></code> is <span class=note><a href=#remove-an-element-from-a-document title="remove an element from a
+ document">removed</a> from a <code><a href=#document>Document</a></code> and is then
+ subsequently garbage collected, this will likely mean (in the
+ absence of other references) that the <a href=#child-browsing-context>child browsing
+ context</a>'s <code><a href=#windowproxy>WindowProxy</a></code> object will become
+ eligble for garbage collection, which will then lead to that
+ <a href=#browsing-context>browsing context</a> being <a href=#a-browsing-context-is-discarded title="a browsing context
+ is discarded">discarded</a>, which will then lead to its
+ <code><a href=#document>Document</a></code> being <a href=#discard-a-document title="discard a
+ document">discarded</a> also. This happens without notice to any
+ scripts running in that <code><a href=#document>Document</a></code>; for example, no
+ <code title=event-unload>unload</code> events are fired (the
+ "<a href=#unload-a-document>unload a document</a>" steps are not run).</span></p>
+
+ </div>
+
+ </div>
+
<div class=example>
<p>Here a blog uses the <code title=attr-iframe-srcdoc><a href=#attr-iframe-srcdoc>srcdoc</a></code> attribute in conjunction
@@ -94732,6 +94761,7 @@
Dimitry Golubovsky,
Dirk Pranke,
Divya Manian,
+ Dmitry Titov,
dolphinling,
Dominique Hazaël-Massieux,
Don Brutzman,
Modified: index
===================================================================
--- index 2010-07-29 23:41:49 UTC (rev 5223)
+++ index 2010-07-30 00:08:04 UTC (rev 5224)
@@ -213,7 +213,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
<hgroup><h1>HTML5 (including next generation additions still in development)</h1>
- <h2 class="no-num no-toc">Draft Standard — 29 July 2010</h2>
+ <h2 class="no-num no-toc">Draft Standard — 30 July 2010</h2>
</hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -21435,6 +21435,35 @@
<code><a href=#windowproxy>WindowProxy</a></code> object will proxy new <code><a href=#window>Window</a></code>
objects for new <code><a href=#document>Document</a></code> objects, but the <code title=attr-iframe-src><a href=#attr-iframe-src>src</a></code> attribute will not change.</p>
+ <div class=impl>
+
+ <div class=note>
+
+ <p><a href=#remove-an-element-from-a-document title="remove an element from a document">Removing</a>
+ an <code><a href=#the-iframe-element>iframe</a></code> from a <code><a href=#document>Document</a></code> does not cause
+ its <a href=#browsing-context>browsing context</a> to be discarded. Indeed, an
+ <code><a href=#the-iframe-element>iframe</a></code>'s span>browsing context can survive its
+ original parent <code><a href=#document>Document</a></code> if its <code><a href=#the-iframe-element>iframe</a></code> is
+ moved to another <code><a href=#document>Document</a></code>.</p>
+
+ <p>On the other hand, if an <code><a href=#the-iframe-element>iframe</a></code> is <span class=note><a href=#remove-an-element-from-a-document title="remove an element from a
+ document">removed</a> from a <code><a href=#document>Document</a></code> and is then
+ subsequently garbage collected, this will likely mean (in the
+ absence of other references) that the <a href=#child-browsing-context>child browsing
+ context</a>'s <code><a href=#windowproxy>WindowProxy</a></code> object will become
+ eligble for garbage collection, which will then lead to that
+ <a href=#browsing-context>browsing context</a> being <a href=#a-browsing-context-is-discarded title="a browsing context
+ is discarded">discarded</a>, which will then lead to its
+ <code><a href=#document>Document</a></code> being <a href=#discard-a-document title="discard a
+ document">discarded</a> also. This happens without notice to any
+ scripts running in that <code><a href=#document>Document</a></code>; for example, no
+ <code title=event-unload>unload</code> events are fired (the
+ "<a href=#unload-a-document>unload a document</a>" steps are not run).</span></p>
+
+ </div>
+
+ </div>
+
<div class=example>
<p>Here a blog uses the <code title=attr-iframe-srcdoc><a href=#attr-iframe-srcdoc>srcdoc</a></code> attribute in conjunction
@@ -87924,6 +87953,7 @@
Dimitry Golubovsky,
Dirk Pranke,
Divya Manian,
+ Dmitry Titov,
dolphinling,
Dominique Hazaël-Massieux,
Don Brutzman,
Modified: source
===================================================================
--- source 2010-07-29 23:41:49 UTC (rev 5223)
+++ source 2010-07-30 00:08:04 UTC (rev 5224)
@@ -22901,6 +22901,36 @@
objects for new <code>Document</code> objects, but the <code
title="attr-iframe-src">src</code> attribute will not change.</p>
+ <div class="impl">
+
+ <div class="note">
+
+ <p><span title="remove an element from a document">Removing</span>
+ an <code>iframe</code> from a <code>Document</code> does not cause
+ its <span>browsing context</span> to be discarded. Indeed, an
+ <code>iframe</code>'s span>browsing context</span> can survive its
+ original parent <code>Document</code> if its <code>iframe</code> is
+ moved to another <code>Document</code>.</p>
+
+ <p>On the other hand, if an <code>iframe</code> is <span <p
+ class="note"><span title="remove an element from a
+ document">removed</span> from a <code>Document</code> and is then
+ subsequently garbage collected, this will likely mean (in the
+ absence of other references) that the <span>child browsing
+ context</span>'s <code>WindowProxy</code> object will become
+ eligble for garbage collection, which will then lead to that
+ <span>browsing context</span> being <span title="a browsing context
+ is discarded">discarded</span>, which will then lead to its
+ <code>Document</code> being <span title="discard a
+ document">discarded</span> also. This happens without notice to any
+ scripts running in that <code>Document</code>; for example, no
+ <code title="event-unload">unload</code> events are fired (the
+ "<span>unload a document</span>" steps are not run).</p>
+
+ </div>
+
+ </div>
+
<div class="example">
<p>Here a blog uses the <code
@@ -108727,6 +108757,7 @@
Dimitry Golubovsky,
Dirk Pranke,
Divya Manian,
+ Dmitry Titov,
dolphinling,
Dominique Hazaël-Massieux,
Don Brutzman,
More information about the Commit-Watchers
mailing list