Intent to Implement and Ship: expose RTCDataChannelEvent and RTCDataChannel

[Luna]

Spec:

Expose RTCDataChannel and RTCDataChannelEvent (with a constructor for RTCDataChannelEvent)

Link to "intent to implement" blink-dev discussion:

This does not affect which events are fired, it means only that the RTCDataChannelEvent interface is exposed and can be used as a constructor.

Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?

Yes

Interoperability and Compatibility Risk

Firefox has this (but they need to update their idl to sync with the most recent spec)

OWP launch tracking bug

https://crbug.com/658428

Entry on the feature dashboard

https://www.chromestatus.com/feature/5673383773601792

No entry was added for RTCDataChannel because it was merely exposed and nothing else about it will change. Because it has no constructor, there isn't much one can do with the RTCDataChannel interface object.

[Philip Jägenstedt]

Oops, spec links went missing:

https://w3c.github.io/webrtc-pc/#idl-def-rtcdatachannel
https://w3c.github.io/webrtc-pc/#idl-def-rtcdatachannelevent

I filed the bug for exposing these based on looking at window.*RTC* in other browsers. That makes me partial, but I believe this is trivial, so LGTM1.

[Rick Byers]

LGTM2

[Chris Harrelson]

LGTM3

LGTM2

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.