12913 2011-06-08 17:21:15 +0000 Close() should throw the same exception as send() for unpaired surrogates 2011-06-21 23:01:26 +0000 1 1 1 Unclassified WebAppsWG WebSocket API (editor: Ian Hickson) unspecified All All RESOLVED FIXED http://dev.w3.org/html5/websockets/#dom-websocket-close P2 normal --- 1 adrianba ian ian mike public-webapps public-webapps-bugzilla oldest_to_newest 49325 0 adrianba 2011-06-08 17:21:15 +0000 In the send() method, the spec [1] says: "If the data argument has any unpaired surrogates, then raise an SYNTAX_ERR exception." This should also apply to the close() method for the reason string [2]. [1] http://dev.w3.org/html5/websockets/#dom-websocket-send [2] http://dev.w3.org/html5/websockets/#dom-websocket-close 50072 1 ian 2011-06-21 22:57:49 +0000 Done. 50073 2 contributor 2011-06-21 23:01:26 +0000 Checked in as WHATWG revision r6270. Check-in comment: Unpaired surrogates should throw an exception in close, like in send(), so we don't ask the protocol to send invalid utf-8 http://html5.org/tools/web-apps-tracker?from=6269&to=6270