support for constructing RTCRtpSender with 'kind' and without transport

Won’t fix Issue #14627286

Details

Author
Philipp H.
Created
Nov 12, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

Newer versions of the ORTC specification allow constructing RTCRtpSender with a ‘kind’ and make the transport argument optional:
http://draft.ortc.org/#rtcrtpsender*

Edge only implements a version of the spec requiring a MediaStreamTrack and the transport:
https://rawgit.com/aboba/edgertc/master/msortc-rs3.html#rtcrtpsender*

Supporting the current specification is required for shimming webrtc 1.0 ontop of ORTC. Currently I am working around this restriction with a javascript shim that does a lazy initialization of the native RTCRtpSender:
https://github.com/otalk/rtcpeerconnection-shim/pull/41

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “James M.”

    • Hello,

      Thank you for providing this information about the issue. We are best suited to test and correct broken features for future releases of MS Edge. Please feel welcome to submit your request at http://uservoice.microsoftedge.com where other developers can up-vote your suggestion.

      Best Wishes,
      The MS Edge Team

    • Microsoft Edge Team

      Changed Status to “Won’t fix”

    You need to sign in to your Microsoft account to add a comment.

    Sign in