[html5] r8243 - [e] (0) Explain 'gone async' Affected topics: HTML

[whatwg at whatwg.org]

Author: ianh
Date: 2013-10-25 16:05:30 -0700 (Fri, 25 Oct 2013)
New Revision: 8243

Modified:
   complete.html
   index
   source
Log:
[e] (0) Explain 'gone async'
Affected topics: HTML

Modified: complete.html
===================================================================
--- complete.html	2013-10-25 14:42:23 UTC (rev 8242)
+++ complete.html	2013-10-25 23:05:30 UTC (rev 8243)
@@ -66430,8 +66430,19 @@
    these steps without affecting the <a href=#prompt-to-unload-a-document>prompt to unload a document</a> algorithm.</li>
    <!-- http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1946 to 1955 -->
 
-   <li><p>Let <var title="">gone async</var> be false.</li>
+   <li>
 
+    <p>Let <var title="">gone async</var> be false.</p>
+
+    <p class=note>The <a href=#navigate-redirect-step><i>handle redirects</i></a> step later in
+    this algorithm can in certain cases jump back to the step labeled <a href=#navigate-fragid-step><i>fragment identifiers</i></a>. Since, between those two steps,
+    this algorithm goes from operating synchronously in the context of the calling <a href=#concept-task title=concept-task>task</a> to operating asynchronously independent of the <a href=#event-loop>event
+    loop</a>, some of the intervening steps need to be able to handle both being synchronous and
+    being asynchronous. The <var title="">gone async</var> flag is thus used to make these steps
+    aware of which mode they are operating in.</p>
+
+   </li>
+
    <li id=navigate-fragid-step><p><i>Fragment identifiers</i>: Apply the <a href=#url-parser>URL parser</a>
    algorithm to the <a href=#absolute-url>absolute URL</a> of the new resource and the <a href="#the-document's-address" title="the
    document's address">address</a> of the <a href=#active-document>active document</a> of the <a href=#browsing-context>browsing
@@ -66542,9 +66553,10 @@
 
    <li><p>Let <var title="">gone async</var> be true.</li>
 
-   <li>
+   <li id=navigate-redirect-step>
 
-    <p>If fetching the resource results in a redirect, and either the <a href=#url>URL</a> of the target
+    <!--CLEANUP-->
+    <p><i>Handle redirects</i>: If fetching the resource results in a redirect, and either the <a href=#url>URL</a> of the target
     of the redirect has the <a href=#same-origin>same origin</a> as the original resource, or the resource is
     being obtained using the POST method or a safe method (in HTTP terms), return to <a href=#navigate-fragid-step>the step labeled <i>fragment identifiers</i></a> with the new
     resource, except that if the <a href=#url>URL</a> of the target of the redirect does not have a
@@ -66564,6 +66576,7 @@
 
    </li>
 
+   <!--CLEANUP: should move this step to above the "handle redirects" step-->
    <li><p>Wait for one or more bytes to be available or for the user agent to establish that the
    resource in question is empty. During this time, the user agent may allow the user to cancel this
    navigation attempt or start other navigation attempts.</li>

Modified: index
===================================================================
--- index	2013-10-25 14:42:23 UTC (rev 8242)
+++ index	2013-10-25 23:05:30 UTC (rev 8243)
@@ -66430,8 +66430,19 @@
    these steps without affecting the <a href=#prompt-to-unload-a-document>prompt to unload a document</a> algorithm.</li>
    <!-- http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1946 to 1955 -->
 
-   <li><p>Let <var title="">gone async</var> be false.</li>
+   <li>
 
+    <p>Let <var title="">gone async</var> be false.</p>
+
+    <p class=note>The <a href=#navigate-redirect-step><i>handle redirects</i></a> step later in
+    this algorithm can in certain cases jump back to the step labeled <a href=#navigate-fragid-step><i>fragment identifiers</i></a>. Since, between those two steps,
+    this algorithm goes from operating synchronously in the context of the calling <a href=#concept-task title=concept-task>task</a> to operating asynchronously independent of the <a href=#event-loop>event
+    loop</a>, some of the intervening steps need to be able to handle both being synchronous and
+    being asynchronous. The <var title="">gone async</var> flag is thus used to make these steps
+    aware of which mode they are operating in.</p>
+
+   </li>
+
    <li id=navigate-fragid-step><p><i>Fragment identifiers</i>: Apply the <a href=#url-parser>URL parser</a>
    algorithm to the <a href=#absolute-url>absolute URL</a> of the new resource and the <a href="#the-document's-address" title="the
    document's address">address</a> of the <a href=#active-document>active document</a> of the <a href=#browsing-context>browsing
@@ -66542,9 +66553,10 @@
 
    <li><p>Let <var title="">gone async</var> be true.</li>
 
-   <li>
+   <li id=navigate-redirect-step>
 
-    <p>If fetching the resource results in a redirect, and either the <a href=#url>URL</a> of the target
+    <!--CLEANUP-->
+    <p><i>Handle redirects</i>: If fetching the resource results in a redirect, and either the <a href=#url>URL</a> of the target
     of the redirect has the <a href=#same-origin>same origin</a> as the original resource, or the resource is
     being obtained using the POST method or a safe method (in HTTP terms), return to <a href=#navigate-fragid-step>the step labeled <i>fragment identifiers</i></a> with the new
     resource, except that if the <a href=#url>URL</a> of the target of the redirect does not have a
@@ -66564,6 +66576,7 @@
 
    </li>
 
+   <!--CLEANUP: should move this step to above the "handle redirects" step-->
    <li><p>Wait for one or more bytes to be available or for the user agent to establish that the
    resource in question is empty. During this time, the user agent may allow the user to cancel this
    navigation attempt or start other navigation attempts.</li>

Modified: source
===================================================================
--- source	2013-10-25 14:42:23 UTC (rev 8242)
+++ source	2013-10-25 23:05:30 UTC (rev 8243)
@@ -74031,8 +74031,21 @@
    these steps without affecting the <span>prompt to unload a document</span> algorithm.</p></li>
    <!-- http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1946 to 1955 -->
 
-   <li><p>Let <var data-x="">gone async</var> be false.</p></li>
+   <li>
 
+    <p>Let <var data-x="">gone async</var> be false.</p>
+
+    <p class="note">The <a href="#navigate-redirect-step"><i>handle redirects</i></a> step later in
+    this algorithm can in certain cases jump back to the step labeled <a
+    href="#navigate-fragid-step"><i>fragment identifiers</i></a>. Since, between those two steps,
+    this algorithm goes from operating synchronously in the context of the calling <span
+    data-x="concept-task">task</span> to operating asynchronously independent of the <span>event
+    loop</span>, some of the intervening steps need to be able to handle both being synchronous and
+    being asynchronous. The <var data-x="">gone async</var> flag is thus used to make these steps
+    aware of which mode they are operating in.</p>
+
+   </li>
+
    <li id="navigate-fragid-step"><p><i>Fragment identifiers</i>: Apply the <span>URL parser</span>
    algorithm to the <span>absolute URL</span> of the new resource and the <span data-x="the
    document's address">address</span> of the <span>active document</span> of the <span>browsing
@@ -74151,9 +74164,10 @@
 
    <li><p>Let <var data-x="">gone async</var> be true.</p></li>
 
-   <li>
+   <li id="navigate-redirect-step">
 
-    <p>If fetching the resource results in a redirect, and either the <span>URL</span> of the target
+    <!--CLEANUP-->
+    <p><i>Handle redirects</i>: If fetching the resource results in a redirect, and either the <span>URL</span> of the target
     of the redirect has the <span>same origin</span> as the original resource, or the resource is
     being obtained using the POST method or a safe method (in HTTP terms), return to <a
     href="#navigate-fragid-step">the step labeled <i>fragment identifiers</i></a> with the new
@@ -74175,6 +74189,7 @@
 
    </li>
 
+   <!--CLEANUP: should move this step to above the "handle redirects" step-->
    <li><p>Wait for one or more bytes to be available or for the user agent to establish that the
    resource in question is empty. During this time, the user agent may allow the user to cancel this
    navigation attempt or start other navigation attempts.</p></li>