[html5] r4379 - [e] (0) Define 'completed loading' in terms of the fetching algorithm. Fixing ht [...]
whatwg at whatwg.org
whatwg at whatwg.org
Wed Nov 25 02:27:45 PST 2009
Author: ianh
Date: 2009-11-25 02:27:44 -0800 (Wed, 25 Nov 2009)
New Revision: 4379
Modified:
complete.html
source
Log:
[e] (0) Define 'completed loading' in terms of the fetching algorithm.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=8190
Modified: complete.html
===================================================================
--- complete.html 2009-11-25 10:15:05 UTC (rev 4378)
+++ complete.html 2009-11-25 10:27:44 UTC (rev 4379)
@@ -64630,12 +64630,13 @@
the stream, the user agent must <a href=#announce-the-connection>announce the
connection</a>.</p>
- <p>If such a resource (with the correct <a href=#mime-type>MIME type</a>)
- completes loading (i.e. either the entire HTTP response body is
- received, or the connection is closed somehow, whether by the server
- or by a network error), the user agent must <a href=#reestablish-the-connection>reestablish the
- connection</a>. This doesn't apply for the error cases that are
- listed below.</p>
+ <p>The <a href=#concept-task title=concept-task>task</a> that the
+ <a href=#networking-task-source>networking task source</a> places on the <a href=#task-queue>task
+ queue</a> once the <a href=#fetch title=fetch>fetching algorithm</a>
+ for such a resource (with the correct <a href=#mime-type>MIME type</a>) has
+ completed must <a href=#reestablish-the-connection>reestablish the connection</a>. This applies
+ whether the connection is closed gracefully or unexpectedly. It
+ doesn't apply for the error conditions listed below.</p>
<p>HTTP 200 OK responses that have a <a href=#content-type>Content-Type</a> other
than <code><a href=#text/event-stream>text/event-stream</a></code> (or some other supported type)
Modified: source
===================================================================
--- source 2009-11-25 10:15:05 UTC (rev 4378)
+++ source 2009-11-25 10:27:44 UTC (rev 4379)
@@ -73692,12 +73692,13 @@
the stream, the user agent must <span>announce the
connection</span>.</p>
- <p>If such a resource (with the correct <span>MIME type</span>)
- completes loading (i.e. either the entire HTTP response body is
- received, or the connection is closed somehow, whether by the server
- or by a network error), the user agent must <span>reestablish the
- connection</span>. This doesn't apply for the error cases that are
- listed below.</p>
+ <p>The <span title="concept-task">task</span> that the
+ <span>networking task source</span> places on the <span>task
+ queue</span> once the <span title="fetch">fetching algorithm</span>
+ for such a resource (with the correct <span>MIME type</span>) has
+ completed must <span>reestablish the connection</span>. This applies
+ whether the connection is closed gracefully or unexpectedly. It
+ doesn't apply for the error conditions listed below.</p>
<p>HTTP 200 OK responses that have a <span>Content-Type</span> other
than <code>text/event-stream</code> (or some other supported type)
More information about the Commit-Watchers
mailing list