W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2011

Re: [Bug 12913] New: Close() should throw the same exception as send() for unpaired surrogates

From: Arthur Barstow <art.barstow@nokia.com>
Date: Fri, 10 Jun 2011 10:04:47 -0400
Message-ID: <4DF2247F.5020500@nokia.com>
To: Adrian Bateman <adrianba@microsoft.com>
CC: public-webapps@w3.org
Adrian - this bug is for the Web Sockets API spec (and not Web Storage), 
correct?

On Jun/8/2011 1:21 PM, ext bugzilla@jessica.w3.org wrote:
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=12913
>
>             Summary: Close() should throw the same exception as send() for
>                      unpaired surrogates
>             Product: WebAppsWG
>             Version: unspecified
>            Platform: All
>                 URL: http://dev.w3.org/html5/websockets/#dom-websocket-clos
>                      e
>          OS/Version: All
>              Status: NEW
>            Severity: normal
>            Priority: P2
>           Component: Web Storage (editor: Ian Hickson)
>          AssignedTo: ian@hixie.ch
>          ReportedBy: adrianba@microsoft.com
>           QAContact: member-webapi-cvs@w3.org
>                  CC: ian@hixie.ch, mike@w3.org, public-webapps@w3.org
>
>
> 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
>
Received on Friday, 10 June 2011 14:05:14 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:45 GMT