This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
> 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
Hixie - would you please provide input on the first issue in this bug i.e. the one about CLOSING? Takeshi - I don't understand what you mean by "missing anchor on reason to its description" (the last issue in this bug) so please elaborate.
Takeshi - nevermind (I now understand your comment about missing a link to the description of the "reason" attribute).
Checked in as WHATWG revision r7295. Check-in comment: Fix some editorial issues for WebSockets http://html5.org/tools/web-apps-tracker?from=7294&to=7295