websocket; hixie: Unpaired surrogates should throw an exception in close, like in send(), so we don't ask the protocol to send invalid utf-8 (whatwg r6270)

websocket; hixie: Unpaired surrogates should throw an exception in
close, like in send(), so we don't ask the protocol to send invalid
utf-8 (whatwg r6270)

http://dev.w3.org/cvsweb/html5/websockets/Overview.html?r1=1.226&r2=1.227&f=h
http://html5.org/tools/web-apps-tracker?from=6269&to=6270

===================================================================
RCS file: /sources/public/html5/websockets/Overview.html,v
retrieving revision 1.226
retrieving revision 1.227
diff -u -d -r1.226 -r1.227
--- Overview.html 21 Jun 2011 22:54:27 -0000 1.226
+++ Overview.html 21 Jun 2011 23:01:21 -0000 1.227
@@ -566,6 +566,10 @@
    <code>INVALID_ACCESS_ERR</code> exception and abort these
    steps.</li>
 
+   <li><p>If the method's second argument has any unpaired surrogates,
+   then throw an <code>SYNTAX_ERR</code> exception and abort these
+   steps.</li>
+
    <li><p>If the method's second argument is present, then let <var title="">reason</var> be the result of encoding that argument as
    UTF-8. If <var title="">reason</var> is longer than 123 bytes, then
    throw an <code>SYNTAX_ERR</code> exception and abort these steps.

Received on Tuesday, 21 June 2011 23:01:28 UTC