We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When I implemented the W3CWebSocket shim I used this version of the WebSocket API in which close() does not accept arguments.
W3CWebSocket
close()
However in the current candidate it accepts "code" and "reason":
http://www.w3.org/TR/websockets/#the-websocket-interface
May be they should be added to the close() method?
The text was updated successfully, but these errors were encountered:
That sounds reasonable, I don't expect it would hurt anything to update to the current draft API. It wouldn't affect backward compatibility.
Sorry, something went wrong.
Reasonable!
However if the cited document is referenced as part of the change, this quote from the document itself should be taken into consideration...
It is inappropriate to cite this document as other than work in progress.
327daad
- W3CWebSocket: really fix #184 and remove slow bind() usages.
f0c1588
No branches or pull requests
When I implemented the
W3CWebSocket
shim I used this version of the WebSocket API in whichclose()
does not accept arguments.However in the current candidate it accepts "code" and "reason":
http://www.w3.org/TR/websockets/#the-websocket-interface
May be they should be added to the
close()
method?The text was updated successfully, but these errors were encountered: