- From: CVS User ihickson <cvsmail@w3.org>
- Date: Mon, 12 Aug 2013 23:36:13 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/eventsource In directory roscoe:/tmp/cvs-serv11667 Modified Files: Overview.html Log Message: Explain how window.stop() affects window.stop() (whatwg r8142) --- /sources/public/html5/eventsource/Overview.html 2013/08/03 16:05:12 1.247 +++ /sources/public/html5/eventsource/Overview.html 2013/08/12 23:36:13 1.248 @@ -216,7 +216,7 @@ <h1>Server-Sent Events</h1> - <h2 class="no-num no-toc" id="editor-s-draft-3-august-2013">Editor's Draft 3 August 2013</h2> + <h2 class="no-num no-toc" id="editor-s-draft-12-august-2013">Editor's Draft 12 August 2013</h2> <dl><dt>Latest Published Version:</dt> <dd><a href="http://www.w3.org/TR/eventsource/">http://www.w3.org/TR/eventsource/</a></dd> <dt>Latest Editor's Draft:</dt> @@ -354,7 +354,7 @@ </dl><p>The W3C <a href="http://www.w3.org/2008/webapps/">Web Applications Working Group</a> is the W3C working group responsible for this specification's progress along the W3C Recommendation track. - This specification is the 3 August 2013 Editor's Draft. + This specification is the 12 August 2013 Editor's Draft. </p> @@ -702,7 +702,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 <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 <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 @@ -722,7 +725,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 <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 <a href="#fail-the-connection">fail the connection</a>.</p> <p>For non-HTTP protocols, UAs should act in equivalent ways.</p>
Received on Monday, 12 August 2013 23:36:14 UTC