This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/ Multipage: http://www.whatwg.org/C#dom-websocket-close Complete: http://www.whatwg.org/c#dom-websocket-close Comment: The first step of close method algorithm isn't clear to understand. Also as I read in RFC http://tools.ietf.org/html/rfc6455#section-7.4.2 codes from 1000 to 4999 can appear in closing message. So I think this section of websocket specification has error. Posted from: 2a00:f480:4:148:69c5:a16b:6412:9c1e User agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; ru; rv:1.9.2.18) Gecko/20110614 Firefox/3.6.18 WebMoney Advisor
The first step of close method algorithm isn't clear to understand. Also as I read in RFC http://tools.ietf.org/html/rfc6455#section-7.4.2 codes from 1000 to 4999 can appear in closing message. But draft states that only 1000 and 3000-4999 are acceptable. So I think this section of websocket specification has error.
Codes 1001-2999 are not codes that it makes sense for a script to specify. Can you elaborate on why that paragraph is hard to understand, though? It seems precise and clear...
1. I've just read http://tools.ietf.org/html/rfc6455#section-11.7. I think you are right. Maybe you are right: all other codes are for internal usage. 2. Is it clear whether "is not an integer equal to 1000 or in the range 3000 to 4999" is "!(1000 AND 3000..4999)" or "!1000 AND 3000..4999"?
"!1000 AND 3000..4999" would be silly, since the first part wouldbe redundant with the second. But to remove all doubt, I've clarified the prose. Thanks for the feedback; send me an e-mail if you would like to be acknowledged by a different name than "Silver Ghost". My e-mail is ian@hixie.ch.
Checked in as WHATWG revision r7698. Check-in comment: Clarify http://html5.org/tools/web-apps-tracker?from=7697&to=7698