https://www.w3.org/Bugs/Public/show_bug.cgi?id=18623
Summary: Editorial issues: Clarify CLOSING, capitalize
websocket, add anchor to reason attribute
Product: WebAppsWG
Version: unspecified
Platform: PC
OS/Version: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: WebSocket API (editor: Ian Hickson)
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
CC: [email protected], [email protected]
> CLOSING (numeric value 2)
> The connection is going through the closing handshake.
The readyState can enter CLOSING also when close() is called before
establishment. In that case, it's not going through closing handshake.
> When the user agent validates the server's response during the "establish a
> WebSocket connection" algorithm, if the status code received from the server
> is not 101 (e.g. it is a redirect), the user agent must fail the websocket
> connection.
websocket -> WebSocket
> If the user agent was required to fail the websocket connection or the
> WebSocket connection is closed with prejudice, fire a simple event named
> error at the WebSocket object. [WSP]
websocket -> WebSocket
> interface CloseEvent : Event {
> readonly attribute boolean wasClean;
> readonly attribute unsigned short code;
> readonly attribute DOMString reason;
> };
missing anchor on reason to its description
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
