- From: <bugzilla@jessica.w3.org>
- Date: Wed, 11 Apr 2012 20:10:50 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16703
Summary: I am suggesting a default value for the "code"
argument to the close method. I am currently
experimenting with this method and noticed that Chrome
and Firefox seem to use different default values. If
I do not specify a code, Chrome appears to use 1005 (
Product: WebAppsWG
Version: unspecified
Platform: Other
URL: http://www.whatwg.org/specs/web-apps/current-work/#top
OS/Version: other
Status: NEW
Severity: normal
Priority: P3
Component: WebSocket API (editor: Ian Hickson)
AssignedTo: ian@hixie.ch
ReportedBy: contributor@whatwg.org
QAContact: public-webapps-bugzilla@w3.org
CC: mike@w3.org, public-webapps@w3.org
Specification: http://dev.w3.org/html5/websockets/
Multipage: http://www.whatwg.org/C#top
Complete: http://www.whatwg.org/c#top
Comment:
I am suggesting a default value for the "code" argument to the close method.
I am currently experimenting with this method and noticed that Chrome and
Firefox seem to use different default values. If I do not specify a code,
Chrome appears to use 1005 (CLOSE_NO_STATUS), while Firefox appears to use
1000 (CLOSE_NORMAL). I tend to agree with using 1005.
Posted from: 67.163.210.178
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.19 (KHTML, like
Gecko) Chrome/18.0.1025.152 Safari/535.19
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 11 April 2012 20:10:56 UTC