How can we improve the Microsoft Edge developer experience?

RTC Data Channels

Data channels allow a web application to send and receive generic application data peer-to-peer.

This feature request is specifically about the *data channel* component of the WebRTC specification. This is separate from Object RTC and WebRTC 1.0 feature requests because the Platform Status site breaks out data channels separately.

RTC Data Channels:

Platform status: https://developer.microsoft.com/en-us/microsoft-edge/platform/status/rtcdatachannels/?q=data%20channels
Uservoice: (this ticket)

Object RTC:

Platform status: https://developer.microsoft.com/en-us/microsoft-edge/platform/status/webrtcobjectrtcapi/?q=Object%20RTC
UserVoice: https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/6263666-webrtc-object-rtc-api

WebRTC 1.0:

Platform status: https://developer.microsoft.com/en-us/microsoft-edge/platform/status/webrtcwebrtcv10api/?q=WebRTC
UserVoice: https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/6508336-webrtc-webrtc-v1-0-api

3,669 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Feross Aboukhadijeh shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    17 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Tufik Chediak commented  ·   ·  Flag as inappropriate

        The Microsoft team really read this comments?, Look like they don't care offer a good browser solution... They only make the developers life painful...
        But you know, in all places always there's the lazy neighbor, that make everything wrong and every body hate but should deal with him. That is edge.

      • Lennart Grahl commented  ·   ·  Flag as inappropriate

        I'm also puzzled why this feature has been separated from ORTC and WebRTC. Data channels are **mandatory to implement**, at least in WebRTC.

        For the same reason we permanently criticise Apple for not supporting both **mandatory** video codecs.

      • Anonymous commented  ·   ·  Flag as inappropriate

        As a result of the lack of data channels in Edge, we actively push our 6 million daily users (and counting) onto Chrome :-(

      • Joshua commented  ·   ·  Flag as inappropriate

        Excluding the not-especially-pertinent 'Update IE' item, this is a top-10 feature request. It is, for me personally, a key differentiator between Chrome/FF and Edge. Some traction here, or any feedback from the dev team about timelines and plans, would be most welcome.

      • Wilhelm W commented  ·   ·  Flag as inappropriate

        Just like @Max previously commented, as of Safari 11 (Sept. 19, 2017) all other major browsers have implemented RTCDataChannels. Is it time to reevaluate the relevance of RTC Data Channels in Edge?

      • Max commented  ·   ·  Flag as inappropriate

        All browsers except Microsoft Edge support DataChannels, but why does Microsoft's Edge still not support DataChannels ???

      • john romero commented  ·   ·  Flag as inappropriate

        There is also « typeof(DataChannel)!=='undefined'||typeof(RTCDataChannel)!=='undefined' » to ensure DataChannel feature is properly available. It could be really useful in edge because some fast paced real time multiplayer game need the datachannel :)

      • Philipp Hancke commented  ·   ·  Flag as inappropriate

        Support can be determined by evaluating whether RTCPeerConnection.prototype.createDataChannel
        exists

      Feedback and Knowledge Base