- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 27 Jul 2012 05:57:04 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/websockets
In directory hutz:/tmp/cvs-serv11119
Modified Files:
Overview.html
Log Message:
Fix some cross-reference issues. (whatwg r7219)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/websockets/Overview.html,v
retrieving revision 1.272
retrieving revision 1.273
diff -u -d -r1.272 -r1.273
--- Overview.html 25 Jul 2012 19:11:18 -0000 1.272
+++ Overview.html 27 Jul 2012 05:57:02 -0000 1.273
@@ -216,7 +216,7 @@
<h1>The WebSocket API</h1>
- <h2 class="no-num no-toc" id="editor-s-draft-25-july-2012">Editor's Draft 25 July 2012</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-27-july-2012">Editor's Draft 27 July 2012</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>
@@ -352,7 +352,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 25 July 2012 Editor's Draft.
+ This specification is the 27 July 2012 Editor's Draft.
</p>
@@ -630,7 +630,7 @@
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-close">close</code> event <a href="#closeWebSocket">as described below</a>.</p>
+ <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>
</li>
@@ -726,7 +726,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-close">close</code> event will eventually fire <a href="#closeWebSocket">as described below</a>.</p>
+ 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>
</dd>
@@ -744,7 +744,7 @@
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-close">close</code> event <a href="#closeWebSocket">as described below</a>.</p>
+ <code title="event-socket-close">close</code> event <a href="#closeWebSocket">as described below</a>.</p>
</dd>
@@ -768,7 +768,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-close">close</code> event <a href="#closeWebSocket">as described below</a>.</p>
+ WebSocket connection is closed</i>, which fires the <code title="event-socket-close">close</code> event <a href="#closeWebSocket">as described below</a>.</p>
</dd>
@@ -784,7 +784,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-close">close</code> event will fire, <a href="#closeWebSocket">as described below</a>.</p>
+ <i>the WebSocket connection is closed</i>, and thus the <code title="event-socket-close">close</code> event will fire, <a href="#closeWebSocket">as described below</a>.</p>
</dd>
@@ -950,7 +950,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-close">close</code>
+ <tr><td><dfn id="handler-websocket-onclose" title="handler-WebSocket-onclose"><code>onclose</code></dfn> <td> <code title="event-socket-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
@@ -1078,7 +1078,7 @@
at the <code><a href="#websocket">WebSocket</a></code> object. <a href="#refsWSP">[WSP]</a></li>
<li><p>Create an event that uses the <code><a href="#closeevent">CloseEvent</a></code>
- interface, with the event type <code title="event-close">close</code>, which does not bubble, is not
+ interface, with the event type <code title="event-socket-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>
@@ -1249,18 +1249,18 @@
(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-close">close</code> events.</p>
+ <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>
<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-close">close</code> events.</p>
+ 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>
<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-close">close</code> events.</p>
+ if there are any event listeners registered for <code title="event-error">error</code> or <code title="event-socket-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
Received on Friday, 27 July 2012 05:57:06 UTC