[Webkit-unassigned] [Bug 67335] WebSocket binaryType should not appear until it is functional

[bugzilla-daemon at webkit.org]

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





--- Comment #5 from Yuta Kitamura <yutak at chromium.org>  2011-09-12 19:55:25 PST ---
For Chromium 14, WebSocket objects don't have binaryType attribute and binary messages aren't supported at all.

For Chromium 15, WebSocket objects do have the attribute and binary data type is fully supported (both sending and receiving). Most recent dev channel build (15.0.874.5) should have this functionality.

For prototype issue, this affects not only WebSockets but also all other interfaces in WebKit. Please open a bug if you feel this needs to be fixed.

I personally think, however, the current WebKit behavior is legitimate (hence WebIDL spec is wrong), because the value of binaryType attribute (and other attributes, such as readyState) is held by each WebSocket object, and changing such attributes shouldn't affect WebSocket prototype.

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