- From: CVS User ihickson <cvsmail@w3.org>
- Date: Wed, 08 Jan 2014 23:55:15 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/websockets
In directory roscoe:/tmp/cvs-serv7001
Modified Files:
Overview.html
Log Message:
Add an event index which acts as the definition of the event names, for editorial purposes (event names are really just strings, so they don't have, or need, a normative definition per se). (whatwg r8385)
--- /sources/public/html5/websockets/Overview.html 2013/11/21 22:57:53 1.305
+++ /sources/public/html5/websockets/Overview.html 2014/01/08 23:55:15 1.306
@@ -216,7 +216,7 @@
<h1>The WebSocket API</h1>
- <h2 class="no-num no-toc" id="editor-s-draft-21-november-2013">Editor's Draft 21 November 2013</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-8-january-2014">Editor's Draft 8 January 2014</h2>
<dl><dt>Latest Published Version:</dt>
<dd><a href="http://www.w3.org/TR/websockets/">http://www.w3.org/TR/websockets/</a></dd>
<dt>Latest Editor's Draft:</dt>
@@ -350,7 +350,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 21 November 2013 Editor's Draft.
+ This specification is the 8 January 2014 Editor's Draft.
</p>
@@ -393,7 +393,7 @@
<li><a href="#feedback-from-the-protocol"><span class="secno">5 </span>Feedback from the protocol</a></li>
<li><a href="#ping-and-pong-frames"><span class="secno">6 </span>Ping and Pong frames</a></li>
<li><a href="#parsing-websocket-urls"><span class="secno">7 </span>Parsing WebSocket URLs</a></li>
- <li><a href="#event-definitions"><span class="secno">8 </span>Event definitions</a></li>
+ <li><a href="#the-closeevent-interfaces"><span class="secno">8 </span>The <code>CloseEvent</code> interfaces</a></li>
<li><a href="#garbage-collection"><span class="secno">9 </span>Garbage collection</a></li>
<li><a href="#references" class="no-num">References</a></li>
<li><a href="#acknowledgements" class="no-num">Acknowledgements</a></ol>
@@ -612,7 +612,7 @@
<p class="note">If the <i>establish a WebSocket connection</i> algorithm fails, it triggers the
<i>fail the WebSocket connection</i> algorithm, which then invokes the <i>close the WebSocket
connection</i> algorithm, which then establishes that <i>the WebSocket connection is closed</i>,
- which fires the <code title="event-socket-close">close</code> event <a href="#closeWebSocket">as
+ which fires the <code title="event-close">close</code> event <a href="#closeWebSocket">as
described below</a>.</p>
</li>
@@ -694,7 +694,7 @@
<p>Do nothing.</p>
<p class="note">The connection is already closing or is already closed. If it has not already,
- a <code title="event-socket-close">close</code> event will eventually fire <a href="#closeWebSocket">as described below</a>.</p>
+ a <code title="event-close">close</code> event will eventually fire <a href="#closeWebSocket">as described below</a>.</p>
</dd>
@@ -708,7 +708,7 @@
<p class="note">The <i>fail the WebSocket connection</i> algorithm invokes the <i>close the
WebSocket connection</i> algorithm, which then establishes that <i>the WebSocket connection is
- closed</i>, which fires the <code title="event-socket-close">close</code> event <a href="#closeWebSocket">as described below</a>.</p>
+ closed</i>, which fires the <code title="event-close">close</code> event <a href="#closeWebSocket">as described below</a>.</p>
</dd>
@@ -729,7 +729,7 @@
<p class="note">The <i>start the WebSocket closing handshake</i> algorithm eventually invokes
the <i>close the WebSocket connection</i> algorithm, which then establishes that <i>the
- WebSocket connection is closed</i>, which fires the <code title="event-socket-close">close</code> event <a href="#closeWebSocket">as described
+ WebSocket connection is closed</i>, which fires the <code title="event-close">close</code> event <a href="#closeWebSocket">as described
below</a>.</p>
</dd>
@@ -743,7 +743,7 @@
<p class="note"><i>The WebSocket closing handshake is started</i>, and will eventually invoke
the <i>close the WebSocket connection</i> algorithm, which will establish that <i>the
- WebSocket connection is closed</i>, and thus the <code title="event-socket-close">close</code>
+ WebSocket connection is closed</i>, and thus the <code title="event-close">close</code>
event will fire, <a href="#closeWebSocket">as described below</a>.</p>
</dd>
@@ -887,7 +887,7 @@
<tbody><tr><td><dfn id="handler-websocket-onopen" title="handler-WebSocket-onopen"><code>onopen</code></dfn> <td> <code title="event-open">open</code>
<tr><td><dfn id="handler-websocket-onmessage" title="handler-WebSocket-onmessage"><code>onmessage</code></dfn> <td> <code title="event-message">message</code>
<tr><td><dfn id="handler-websocket-onerror" title="handler-WebSocket-onerror"><code>onerror</code></dfn> <td> <code title="event-error">error</code>
- <tr><td><dfn id="handler-websocket-onclose" title="handler-WebSocket-onclose"><code>onclose</code></dfn> <td> <code title="event-socket-close">close</code>
+ <tr><td><dfn id="handler-websocket-onclose" title="handler-WebSocket-onclose"><code>onclose</code></dfn> <td> <code title="event-close">close</code>
</table><h2 id="feedback-from-the-protocol"><span class="secno">5 </span>Feedback from the protocol</h2>
<p>When <i>the WebSocket connection is established</i>, the user agent must <span>queue a
@@ -1002,7 +1002,7 @@
object. <a href="#refsWSP">[WSP]</a></li>
<li><p>Create a <span title="concept-events-trusted">trusted</span> event that uses the
- <code><a href="#closeevent">CloseEvent</a></code> interface, with the event type <code title="event-socket-close">close</code>, which does not bubble, is not cancelable, has no default
+ <code><a href="#closeevent">CloseEvent</a></code> interface, with the event type <code title="event-close">close</code>, which does not bubble, is not cancelable, has no default
action, whose <code title="dom-CloseEvent-wasClean"><a href="#dom-closeevent-wasclean">wasClean</a></code> attribute is initialized to
true if the connection closed <i title="">cleanly</i> and false otherwise, whose <code title="dom-CloseEvent-code"><a href="#dom-closeevent-code">code</a></code> attribute is initialized to <i>the WebSocket connection
close code</i>, and whose <code title="dom-CloseEvent-reason"><a href="#dom-closeevent-reason">reason</a></code> attribute is
@@ -1112,7 +1112,7 @@
<li><p>Return <var title="">host</var>, <var title="">port</var>, <var title="">resource
name</var>, and <var title="">secure</var>.</li>
- </ol><h2 id="event-definitions"><span class="secno">8 </span>Event definitions</h2>
+ </ol><h2 id="the-closeevent-interfaces"><span class="secno">8 </span>The <code><a href="#closeevent">CloseEvent</a></code> interfaces</h2>
<pre class="idl">[Constructor(DOMString type, optional <a href="#closeeventinit">CloseEventInit</a> eventInitDict)]
interface <dfn id="closeevent">CloseEvent</dfn> : <span>Event</span> {
@@ -1147,17 +1147,17 @@
attribute's value was set to <code title="dom-WebSocket-CONNECTING"><a href="#dom-websocket-connecting">CONNECTING</a></code> (0) as of
the last time the <span>event loop</span> started executing a <span title="concept-task">task</span> must not be garbage collected if there are any event listeners
registered for <code title="event-open">open</code> events, <code title="event-message">message</code> events, <code title="event-error">error</code> events, or
- <code title="event-socket-close">close</code> events.</p>
+ <code title="event-close">close</code> events.</p>
<p>A <code><a href="#websocket">WebSocket</a></code> object whose <code title="dom-WebSocket-readyState"><a href="#dom-websocket-readystate">readyState</a></code>
attribute's value was set to <code title="dom-WebSocket-OPEN"><a href="#dom-websocket-open">OPEN</a></code> (1) as of the last time
the <span>event loop</span> started executing a <span title="concept-task">task</span> must not be
- garbage collected if there are any event listeners registered for <code title="event-message">message</code> events, <code title="event-error">error</code>, or <code title="event-socket-close">close</code> events.</p>
+ garbage collected if there are any event listeners registered for <code title="event-message">message</code> events, <code title="event-error">error</code>, or <code title="event-close">close</code> events.</p>
<p>A <code><a href="#websocket">WebSocket</a></code> object whose <code title="dom-WebSocket-readyState"><a href="#dom-websocket-readystate">readyState</a></code>
attribute's value was set to <code title="dom-WebSocket-CLOSING"><a href="#dom-websocket-closing">CLOSING</a></code> (2) as of the last
time the <span>event loop</span> started executing a <span title="concept-task">task</span> must
- not be garbage collected if there are any event listeners registered for <code title="event-error">error</code> or <code title="event-socket-close">close</code> events.</p>
+ not be garbage collected if there are any event listeners registered for <code title="event-error">error</code> or <code title="event-close">close</code> events.</p>
<p>A <code><a href="#websocket">WebSocket</a></code> object with <i title="the WebSocket connection is established">an
established connection</i> that has data queued to be transmitted to the network must not be
Received on Wednesday, 8 January 2014 23:55:16 UTC