SSE; hixie: withCredentials in EventSource should also affect reconnections. (whatwg r6841)

SSE; hixie: withCredentials in EventSource should also affect
reconnections. (whatwg r6841)

http://dev.w3.org/cvsweb/html5/eventsource/Overview.html?r1=1.208&r2=1.209&f=h
http://html5.org/tools/web-apps-tracker?from=6840&to=6841

===================================================================
RCS file: /sources/public/html5/eventsource/Overview.html,v
retrieving revision 1.208
retrieving revision 1.209
diff -u -d -r1.208 -r1.209
--- Overview.html 28 Nov 2011 23:04:57 -0000 1.208
+++ Overview.html 2 Dec 2011 22:58:04 -0000 1.209
@@ -215,7 +215,7 @@
 
    <h1>Server-Sent Events</h1>
    
-   <h2 class="no-num no-toc" id="editor-s-draft-28-november-2011">Editor's Draft 28 November 2011</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-2-december-2011">Editor's Draft 2 December 2011</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>
@@ -323,7 +323,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 28 November 2011 Editor's Draft.
+  This specification is the 2 December 2011 Editor's Draft.
   </p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
   February 2004 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/42538/status" rel="disclosure">public list of
   any patent disclosures</a> made in connection with the deliverables
@@ -493,12 +493,12 @@
    these steps in the background (without blocking scripts).</li>
 
    <li>
-
     <p>Do a <span>potentially CORS-enabled fetch</span> of the
     resulting <span>absolute URL</span>, with the <i>mode</i> being
     <var title="">CORS mode</var>, and the <i title="">origin</i>
-    being the <span>entry script</span>'s <span>origin</span>, and process the
-    resource obtained in this fashion, if any, as described below.</p>
+    being the <span>entry script</span>'s <span>origin</span>,
+    and process the resource obtained in this fashion, if any, as
+    described below.</p>
 
     <p class="note">The definition of the <span title="fetch">fetching</span> algorithm (which is used by CORS) is
     such that if the browser is already fetching the resource
@@ -640,12 +640,11 @@
 
      <li><p>Perform a <span>potentially CORS-enabled fetch</span> of
      the <span>absolute URL</span> of the event source resource, with
-     the <i>mode</i> being <span title="attr-crossorigin-use-credentials">Use Credentials</span>,
-     and the <i title="">origin</i> being the same as the
-     <span>origin</span> used in the original request triggered by the
-     <code title="dom-EventSource"><a href="#dom-eventsource">EventSource()</a></code>
-     constructor, and process the resource obtained in this fashion, if
-     any, as described earlier in this section.</li>
+     the <i>mode</i> and
+     the <i title="">origin</i> being the same as those used in the
+     original request triggered by the <code title="dom-EventSource"><a href="#dom-eventsource">EventSource()</a></code> constructor, and
+     process the resource obtained in this fashion, if any, as
+     described earlier in this section.</li>
 
     </ol></li>

Received on Wednesday, 14 December 2011 02:00:49 UTC