[html5] r8475 - [e] (0) Make the EventSource processing model a mite more generic to allow other [...]
whatwg at whatwg.org
whatwg at whatwg.org
Fri Feb 7 16:31:13 PST 2014
Author: ianh
Date: 2014-02-07 16:31:12 -0800 (Fri, 07 Feb 2014)
New Revision: 8475
Modified:
complete.html
index
source
Log:
[e] (0) Make the EventSource processing model a mite more generic to allow other user agent types to implement this spec.
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=23693
Affected topics: HTML
Modified: complete.html
===================================================================
--- complete.html 2014-02-07 17:51:47 UTC (rev 8474)
+++ complete.html 2014-02-08 00:31:12 UTC (rev 8475)
@@ -298,7 +298,7 @@
<header class=head id=head><p><a href=http://www.whatwg.org/ class=logo><img width=101 src=/images/logo alt=WHATWG height=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
- <h2 class="no-num no-toc">Living Standard — Last Updated 7 February 2014</h2>
+ <h2 class="no-num no-toc">Living Standard — Last Updated 8 February 2014</h2>
</hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
@@ -79796,8 +79796,8 @@
<dt>If the field name is "reconnect"</dt>
- <dd><p>If the field value is the empty string, then: <a href="#dispatchMessage">dispatch the
- event</a> as defined below, and then drop the connection and immediately reconnect as if the
+ <dd><p>If the field value is the empty string, then: <span>dispatch the
+ event</span> as defined below, and then drop the connection and immediately reconnect as if the
<span title="concept-event-stream-reconnection-time">reconnection time</span> was zero for this
one time.</p></dd>
@@ -79807,9 +79807,12 @@
<dd><p>The field is ignored.</dd>
- </dl><p id=dispatchMessage>When the user agent is required to <dfn title="">dispatch the event</dfn>,
- then the user agent must act as follows:
+ </dl><p>When the user agent is required to <dfn id=dispatchMessage>dispatch the
+ event</dfn>, the user agent must process the <var title="">data</var> buffer, the <var title="">event type</var> buffer, and the <var title="">last event ID</var> buffer using steps
+ appropriate for the user agent.</p>
+ <p>For Web browsers, the appropriate steps to <a href=#dispatchMessage>dispatch the event</a> are as follows:</p>
+
<ol><li><p>Set the <a href=#concept-event-stream-last-event-id title=concept-event-stream-last-event-id>last event ID string</a> of
the event source to the value of the <var title="">last event ID</var> buffer. The buffer does
not get reset, so the <a href=#concept-event-stream-last-event-id title=concept-event-stream-last-event-id>last event ID
@@ -79847,6 +79850,8 @@
event's <code title=dom-MessageEvent-lastEventId><a href=#dom-messageevent-lasteventid>lastEventId</a></code> field will be set to the
value of whatever the last seen "id" field was.</p>
+ <p>For other user agents, the appropriate steps to <a href=#dispatchMessage>dispatch the event</a> are
+ implementation dependent, but at a minimum they must set the <var title="">data</var> and <var title="">event type</var> buffers to the empty string before returning.</p>
<div class=example>
Modified: index
===================================================================
--- index 2014-02-07 17:51:47 UTC (rev 8474)
+++ index 2014-02-08 00:31:12 UTC (rev 8475)
@@ -298,7 +298,7 @@
<header class=head id=head><p><a href=http://www.whatwg.org/ class=logo><img width=101 src=/images/logo alt=WHATWG height=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
- <h2 class="no-num no-toc">Living Standard — Last Updated 7 February 2014</h2>
+ <h2 class="no-num no-toc">Living Standard — Last Updated 8 February 2014</h2>
</hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
@@ -79796,8 +79796,8 @@
<dt>If the field name is "reconnect"</dt>
- <dd><p>If the field value is the empty string, then: <a href="#dispatchMessage">dispatch the
- event</a> as defined below, and then drop the connection and immediately reconnect as if the
+ <dd><p>If the field value is the empty string, then: <span>dispatch the
+ event</span> as defined below, and then drop the connection and immediately reconnect as if the
<span title="concept-event-stream-reconnection-time">reconnection time</span> was zero for this
one time.</p></dd>
@@ -79807,9 +79807,12 @@
<dd><p>The field is ignored.</dd>
- </dl><p id=dispatchMessage>When the user agent is required to <dfn title="">dispatch the event</dfn>,
- then the user agent must act as follows:
+ </dl><p>When the user agent is required to <dfn id=dispatchMessage>dispatch the
+ event</dfn>, the user agent must process the <var title="">data</var> buffer, the <var title="">event type</var> buffer, and the <var title="">last event ID</var> buffer using steps
+ appropriate for the user agent.</p>
+ <p>For Web browsers, the appropriate steps to <a href=#dispatchMessage>dispatch the event</a> are as follows:</p>
+
<ol><li><p>Set the <a href=#concept-event-stream-last-event-id title=concept-event-stream-last-event-id>last event ID string</a> of
the event source to the value of the <var title="">last event ID</var> buffer. The buffer does
not get reset, so the <a href=#concept-event-stream-last-event-id title=concept-event-stream-last-event-id>last event ID
@@ -79847,6 +79850,8 @@
event's <code title=dom-MessageEvent-lastEventId><a href=#dom-messageevent-lasteventid>lastEventId</a></code> field will be set to the
value of whatever the last seen "id" field was.</p>
+ <p>For other user agents, the appropriate steps to <a href=#dispatchMessage>dispatch the event</a> are
+ implementation dependent, but at a minimum they must set the <var title="">data</var> and <var title="">event type</var> buffers to the empty string before returning.</p>
<div class=example>
Modified: source
===================================================================
--- source 2014-02-07 17:51:47 UTC (rev 8474)
+++ source 2014-02-08 00:31:12 UTC (rev 8475)
@@ -89327,7 +89327,7 @@
<dt>If the line is empty (a blank line)</dt>
- <dd><p><a href="#dispatchMessage">Dispatch the event</a>, as defined below.</p></dd>
+ <dd><p><span>Dispatch the event</span>, as defined below.</p></dd>
<dt>If the line starts with a U+003A COLON character (:)</dt>
@@ -89417,8 +89417,8 @@
<dt>If the field name is "reconnect"</dt>
- <dd><p>If the field value is the empty string, then: <a href="#dispatchMessage">dispatch the
- event</a> as defined below, and then drop the connection and immediately reconnect as if the
+ <dd><p>If the field value is the empty string, then: <span>dispatch the
+ event</span> as defined below, and then drop the connection and immediately reconnect as if the
<span data-x="concept-event-stream-reconnection-time">reconnection time</span> was zero for this
one time.</p></dd>
@@ -89431,9 +89431,13 @@
</dl>
- <p id="dispatchMessage">When the user agent is required to <dfn data-x="">dispatch the event</dfn>,
- then the user agent must act as follows:
+ <p>When the user agent is required to <dfn id="dispatchMessage">dispatch the
+ event</dfn>, the user agent must process the <var data-x="">data</var> buffer, the <var
+ data-x="">event type</var> buffer, and the <var data-x="">last event ID</var> buffer using steps
+ appropriate for the user agent.</p>
+ <p>For Web browsers, the appropriate steps to <span>dispatch the event</span> are as follows:</p>
+
<ol>
<li><p>Set the <span data-x="concept-event-stream-last-event-id">last event ID string</span> of
@@ -89482,6 +89486,9 @@
event's <code data-x="dom-MessageEvent-lastEventId">lastEventId</code> field will be set to the
value of whatever the last seen "id" field was.</p>
+ <p>For other user agents, the appropriate steps to <span>dispatch the event</span> are
+ implementation dependent, but at a minimum they must set the <var data-x="">data</var> and <var
+ data-x="">event type</var> buffers to the empty string before returning.</p>
<div class="example">
More information about the Commit-Watchers
mailing list