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

[bugzilla-daemon at webkit.org]

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

           Summary: WebSocket binaryType should not appear until it is
                    functional
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: New Bugs
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: webkit at martintribe.org
                CC: yutak at chromium.org


In Chrome/Chromium 15.0.868.0 (Developer Build 99067 Linux) I note that the binaryType property of the WebSocket instance is visible and set to "blob". It can also be set to "arraybuffer". This would be fine except for the fact that it is in fact non-functional and worse it is misleading.

This behavior means that currently there is no way to do object detection to determine if WebSocket supports binary data or not. This applies to Chrome 14 and 15 (I'm not sure exactly which WebKit builds that equates to). The support for arraybuffers and blobs in the WebSocket API has just landed (https://bugs.webkit.org/show_bug.cgi?id=67180, https://bugs.webkit.org/show_bug.cgi?id=67115) so the issue is going away, but for the intermediate builds (where binaryType appeared as a property but is non-functional) this is a major issue.

Please backport a fix so that binaryType doesn't show up until it actually does something.

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