[html5] r3260 - [] (0) Make document.open() handle timeouts and database transactions more cleanly.

[whatwg at whatwg.org]

Author: ianh
Date: 2009-06-15 15:55:07 -0700 (Mon, 15 Jun 2009)
New Revision: 3260

Modified:
   index
   source
Log:
[] (0) Make document.open() handle timeouts and database transactions more cleanly.

Modified: index
===================================================================
--- index	2009-06-15 22:30:45 UTC (rev 3259)
+++ index	2009-06-15 22:55:07 UTC (rev 3260)
@@ -8554,20 +8554,6 @@
    document to be unloaded</a>, then these steps must be
    aborted.</li>
 
-   <!-- XXX should some task sources be emptied here? e.g. what about
-   timeouts that fired after this algorithm started but before the
-   list of timeouts was cleared in the previous step? or database
-   transaction callbacks that were queued after the task that started
-   this algorithm?
-
-   This is what the 'discard a document' algorithm does:
-
-     "any <span title="concept-task">tasks</span> associated with the
-     <code>Document</code> in any <span>task source</span> must be
-     removed without being run"
-
-    -->
-
    <li><p>If the document has an <a href=#active-parser>active parser</a>, then
    abort that parser, and throw away any pending content in the input
    stream. <span class=XXX>what about if it doesn't, because it's
@@ -8578,6 +8564,12 @@
    <li><p>Unregister all event listeners registered on the
    <code>Document</code> node and its descendants.</p>
 
+   <li><p>Remove any <a href=#concept-task title=concept-task>tasks</a>
+   associated with the <code>Document</code> in any <a href=#task-source>task
+   source</a>.</li> <!-- removes callbacks that fired between
+   this algorithm starting and the times and databases being aborted
+   in the "unload" step above -->
+
    <li><p>Remove all child nodes of the document, without firing any
    mutation events.</li> <!-- as of 2009-03-30, only WebKit fired
    mutation events here. -->

Modified: source
===================================================================
--- source	2009-06-15 22:30:45 UTC (rev 3259)
+++ source	2009-06-15 22:55:07 UTC (rev 3260)
@@ -8702,20 +8702,6 @@
    document to be unloaded</span>, then these steps must be
    aborted.</p></li>
 
-   <!-- XXX should some task sources be emptied here? e.g. what about
-   timeouts that fired after this algorithm started but before the
-   list of timeouts was cleared in the previous step? or database
-   transaction callbacks that were queued after the task that started
-   this algorithm?
-
-   This is what the 'discard a document' algorithm does:
-
-     "any <span title="concept-task">tasks</span> associated with the
-     <code>Document</code> in any <span>task source</span> must be
-     removed without being run"
-
-    -->
-
    <li><p>If the document has an <span>active parser</span>, then
    abort that parser, and throw away any pending content in the input
    stream. <span class="XXX">what about if it doesn't, because it's
@@ -8726,6 +8712,12 @@
    <li><p>Unregister all event listeners registered on the
    <code>Document</code> node and its descendants.</p>
 
+   <li><p>Remove any <span title="concept-task">tasks</span>
+   associated with the <code>Document</code> in any <span>task
+   source</span>.</p></li> <!-- removes callbacks that fired between
+   this algorithm starting and the times and databases being aborted
+   in the "unload" step above -->
+
    <li><p>Remove all child nodes of the document, without firing any
    mutation events.</p></li> <!-- as of 2009-03-30, only WebKit fired
    mutation events here. -->