[w3c/websockets] Add BinaryType enum, and use it for the binaryType attribute (#1)

The current published version of the WebSocket API specification on W3C side uses a `DOMString` for the `binaryType` attribute, that throws a `SyntaxError` on setting.

The WHATWG version uses a `BinaryType` enum for that attribute, which simply ignores invalid values:
https://html.spec.whatwg.org/multipage/comms.html#binarytype

Both Firefox and Chrome seem to use the enum version. What is the plan to align the W3C spec?

Note this would impact the [WebRTC](https://w3c.github.io/webrtc-pc/) and the [Presentation API](https://w3c.github.io/presentation-api/) specs. Both specs follow a similar design and define a `binaryType` attribute as well. In WebRTC, it is defined as a `DOMString` for now. The Presentation API rather uses an enum, and defines the `BinaryType` enum. The Presentation API would reference the definition in the Web Socket API if it existed.




-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/websockets/issues/1