- From: <bugzilla@jessica.w3.org>
- Date: Tue, 08 May 2012 19:31:01 +0000
- To: public-webapps@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16999 Summary: Clarify JS type for empty close reason Product: WebAppsWG Version: unspecified Platform: All OS/Version: All Status: NEW Severity: minor Priority: P2 Component: WebSocket API (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: jduell.mcbugs@gmail.com QAContact: public-webapps-bugzilla@w3.org CC: mike@w3.org, public-webapps@w3.org I don't believe the Web socket spec is clear on this: If there is no close 'reason' passed from the server in the protocol (which on a network frame level is different than sending an empty Unicode string), should we set the close event's 'reason' field to 'undefined', or to an empty string? Right now Firefox is setting it to an empty string. Logically, I feel it ought to be 'undefined'. But I don't see much harm in it being an empty string. Either way the spec should be clear about it. -- 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.
Received on Tuesday, 8 May 2012 19:31:04 UTC