websocket; hixie: Make <figcaption> accept flow again. Also clarify an exception handling case that was ambiguous. (whatwg r5054)

websocket; hixie: Make <figcaption> accept flow again. Also clarify an
exception handling case that was ambiguous. (whatwg r5054)

http://dev.w3.org/cvsweb/html5/websockets/Overview.html?r1=1.171&r2=1.172&f=h
http://html5.org/tools/web-apps-tracker?from=5053&to=5054

===================================================================
RCS file: /sources/public/html5/websockets/Overview.html,v
retrieving revision 1.171
retrieving revision 1.172
diff -u -d -r1.171 -r1.172
--- Overview.html 15 Apr 2010 01:00:35 -0000 1.171
+++ Overview.html 15 Apr 2010 07:12:26 -0000 1.172
@@ -443,8 +443,9 @@
   <code title="dom-WebSocket-CONNECTING"><a href="#dom-websocket-connecting">CONNECTING</a></code> (0).<p>The <dfn id="dom-websocket-send" title="dom-WebSocket-send"><code>send(<var title="">data</var>)</code></dfn> method transmits data using the
   connection. If the <code title="dom-WebSocket-readyState"><a href="#dom-websocket-readystate">readyState</a></code> attribute is
   <code title="dom-WebSocket-CONNECTING"><a href="#dom-websocket-connecting">CONNECTING</a></code>, it must
-  raise an <code>INVALID_STATE_ERR</code> exception. If the <var title="">data</var> argument has any unpaired surrogates, then it
-  must raise <code>SYNTAX_ERR</code>. If the connection is
+  raise an <code>INVALID_STATE_ERR</code> exception. Otherwise, if the
+  <var title="">data</var> argument has any unpaired surrogates, then
+  it must raise <code>SYNTAX_ERR</code>. If the connection is
   established, and the string has no unpaired surrogates, and <span title="the WebSocket closing handshake has started">the WebSocket
   closing handshake has not yet started</span>, then the user agent
   must <span>send <var title="">data</var> using the

Received on Thursday, 15 April 2010 07:13:13 UTC