[html5] r8142 - [e] (0) Explain how window.stop() affects window.stop() Fixing https://www.w3.or [...]
whatwg at whatwg.org
whatwg at whatwg.org
Mon Aug 12 16:36:10 PDT 2013
Author: ianh
Date: 2013-08-12 16:36:09 -0700 (Mon, 12 Aug 2013)
New Revision: 8142
Modified:
complete.html
index
source
Log:
[e] (0) Explain how window.stop() affects window.stop()
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=22604
Affected topics: HTML
Modified: complete.html
===================================================================
--- complete.html 2013-08-12 23:14:45 UTC (rev 8141)
+++ complete.html 2013-08-12 23:36:09 UTC (rev 8142)
@@ -81411,7 +81411,7 @@
cross-origin request</a> mechanism.) User agents should ignore HTTP cache headers in the
response, never caching event sources.</p>
- <hr><p>As data is received, the <a href=#concept-task title=concept-task>tasks</a> queued by the <a href=#networking-task-source>networking
+ <hr><!--CLEANUP--><p>As data is received, the <a href=#concept-task title=concept-task>tasks</a> queued by the <a href=#networking-task-source>networking
task source</a> to handle the data must act as follows.</p>
<p>HTTP 200 OK responses with a <a href=#content-type>Content-Type</a> header specifying the type
@@ -81426,7 +81426,10 @@
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 cause the user agent to
asynchronously <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 except
+ closed gracefully or unexpectedly (but does not apply when the <a href=#fetch>fetch</a> algorithm is
+ canceled by the user agent, e.g. in response to <code title=dom-window-stop><a href=#dom-window-stop>window.stop()</a></code>,
+ since in those cases the final <a href=#concept-task title=concept-task>task</a> is actually discarded).
+ It doesn't apply for the error conditions listed below except
where explicitly specified.</p>
<p>HTTP 200 OK responses that have a <a href=#content-type>Content-Type</a> specifying an unsupported type, or
@@ -81447,7 +81450,9 @@
being established in the first place (e.g. DNS errors), must cause the user agent to
asynchronously <a href=#reestablish-the-connection>reestablish the connection</a>.</p>
- <p id=event-source-fail-reasons>Any other HTTP response code not listed here must cause the user
+ <p id=event-source-fail-reasons>Any other HTTP response code not listed here, as well as the
+ cancelation of the <a href=#fetch>fetch</a> algorithm by the user agent (e.g. in response to
+ <code title=dom-window-stop><a href=#dom-window-stop>window.stop()</a></code> or the user canceling the network connection manually) must cause the user
agent to <a href=#fail-the-connection>fail the connection</a>.</p> <!-- including: HTTP 201 Created, 202 Accepted, 203
Non-Authoritative Information, 204 No Content, 205 Reset Content, 206 Partial Content, 300
Multiple Choices, 304 Not Modified, 400 Bad Request, 403 Forbidden, 404 Not Found, 405 Method Not
@@ -103769,6 +103774,7 @@
Travis Leithead,
Tyler Close,
Victor Carbune,
+ Vitya Muhachev,
Vladimir Katardjiev,
Vladimir Vukićević,
voracity,
Modified: index
===================================================================
--- index 2013-08-12 23:14:45 UTC (rev 8141)
+++ index 2013-08-12 23:36:09 UTC (rev 8142)
@@ -81411,7 +81411,7 @@
cross-origin request</a> mechanism.) User agents should ignore HTTP cache headers in the
response, never caching event sources.</p>
- <hr><p>As data is received, the <a href=#concept-task title=concept-task>tasks</a> queued by the <a href=#networking-task-source>networking
+ <hr><!--CLEANUP--><p>As data is received, the <a href=#concept-task title=concept-task>tasks</a> queued by the <a href=#networking-task-source>networking
task source</a> to handle the data must act as follows.</p>
<p>HTTP 200 OK responses with a <a href=#content-type>Content-Type</a> header specifying the type
@@ -81426,7 +81426,10 @@
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 cause the user agent to
asynchronously <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 except
+ closed gracefully or unexpectedly (but does not apply when the <a href=#fetch>fetch</a> algorithm is
+ canceled by the user agent, e.g. in response to <code title=dom-window-stop><a href=#dom-window-stop>window.stop()</a></code>,
+ since in those cases the final <a href=#concept-task title=concept-task>task</a> is actually discarded).
+ It doesn't apply for the error conditions listed below except
where explicitly specified.</p>
<p>HTTP 200 OK responses that have a <a href=#content-type>Content-Type</a> specifying an unsupported type, or
@@ -81447,7 +81450,9 @@
being established in the first place (e.g. DNS errors), must cause the user agent to
asynchronously <a href=#reestablish-the-connection>reestablish the connection</a>.</p>
- <p id=event-source-fail-reasons>Any other HTTP response code not listed here must cause the user
+ <p id=event-source-fail-reasons>Any other HTTP response code not listed here, as well as the
+ cancelation of the <a href=#fetch>fetch</a> algorithm by the user agent (e.g. in response to
+ <code title=dom-window-stop><a href=#dom-window-stop>window.stop()</a></code> or the user canceling the network connection manually) must cause the user
agent to <a href=#fail-the-connection>fail the connection</a>.</p> <!-- including: HTTP 201 Created, 202 Accepted, 203
Non-Authoritative Information, 204 No Content, 205 Reset Content, 206 Partial Content, 300
Multiple Choices, 304 Not Modified, 400 Bad Request, 403 Forbidden, 404 Not Found, 405 Method Not
@@ -103769,6 +103774,7 @@
Travis Leithead,
Tyler Close,
Victor Carbune,
+ Vitya Muhachev,
Vladimir Katardjiev,
Vladimir Vukićević,
voracity,
Modified: source
===================================================================
--- source 2013-08-12 23:14:45 UTC (rev 8141)
+++ source 2013-08-12 23:36:09 UTC (rev 8142)
@@ -90712,6 +90712,7 @@
response, never caching event sources.</p>
<hr>
+<!--CLEANUP-->
<p>As data is received, the <span title="concept-task">tasks</span> queued by the <span>networking
task source</span> to handle the data must act as follows.</p>
@@ -90728,7 +90729,10 @@
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 cause the user agent to
asynchronously <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 except
+ closed gracefully or unexpectedly (but does not apply when the <span>fetch</span> algorithm is
+ canceled by the user agent, e.g. in response to <code title="dom-window-stop">window.stop()</code>,
+ since in those cases the final <span title="concept-task">task</span> is actually discarded).
+ It doesn't apply for the error conditions listed below except
where explicitly specified.</p>
<p>HTTP 200 OK responses that have a <span>Content-Type</span> specifying an unsupported type, or
@@ -90749,7 +90753,9 @@
being established in the first place (e.g. DNS errors), must cause the user agent to
asynchronously <span>reestablish the connection</span>.</p>
- <p id="event-source-fail-reasons">Any other HTTP response code not listed here must cause the user
+ <p id="event-source-fail-reasons">Any other HTTP response code not listed here, as well as the
+ cancelation of the <span>fetch</span> algorithm by the user agent (e.g. in response to
+ <code title="dom-window-stop">window.stop()</code> or the user canceling the network connection manually) must cause the user
agent to <span>fail the connection</span>.</p> <!-- including: HTTP 201 Created, 202 Accepted, 203
Non-Authoritative Information, 204 No Content, 205 Reset Content, 206 Partial Content, 300
Multiple Choices, 304 Not Modified, 400 Bad Request, 403 Forbidden, 404 Not Found, 405 Method Not
@@ -116254,6 +116260,7 @@
Travis Leithead,
Tyler Close,
Victor Carbune,
+ Vitya Muhachev,
Vladimir Katardjiev,
Vladimir Vukićević,
voracity,
More information about the Commit-Watchers
mailing list