[Webkit-unassigned] [Bug 81072] [WebSocket]Browser should use 1000 as status code when WebSocket API close is called without status code parameter.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue May 8 00:17:53 PDT 2012


https://bugs.webkit.org/show_bug.cgi?id=81072





--- Comment #10 from Li Yin <li.yin at intel.com>  2012-05-08 00:17:53 PST ---
(In reply to comment #9)
> API spec author said in the w3c thread in https://www.w3.org/Bugs/Public/show_bug.cgi?id=16703,
> 
> > Ian 'Hixie' Hickson 2012-05-02 20:09:29 UTC
> > As far as I can tell, the spec is clear on this. If there's no argument, then
> > no close code is passed to the protocol. The protocol spec defines what to do
> > in that case.
> 
> And Firefox is going to fix the behavior.
> https://bugzilla.mozilla.org/show_bug.cgi?id=748580
> 
> So, I'd like to close this issue.

Okay, thanks.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list