Issue metadata
Sign in to add a comment
|
Implement RTCRtpSender and RTCRtpReceiver |
||||||||||||||||||||||||
Issue descriptionhttps://w3c.github.io/webrtc-pc/#rtcrtpsender-interface https://w3c.github.io/webrtc-pc/#rtcrtpreceiver-interface These two interfaces are exposed in Edge and Firefox, although no testing has been done of the implementation. This was found via https://docs.google.com/spreadsheets/d/1Fqv1JyadCDGMJ91GdIYPQicI97ELIHabwUfxFQv-jLU/edit#gid=0
,
Oct 26 2016
,
Oct 26 2016
,
Nov 10 2016
FYI, I created a tracking feature specifically for senders/receivers which covers a small subset of the functionality, mainly to allow an application to switch tracks: https://www.chromestatus.com/features/5347809238712320
,
Nov 10 2016
,
Nov 10 2016
,
Nov 11 2016
Why is this item using the "UnoffiicalSpec" label? Is there a tracking bug for the "skeleton" Sender/Receiver feature? If so, that should probably be listed as a blocker for this one.
,
Nov 11 2016
Just misclicked. The "OfficialSpec" label is still desired for these issues, correct?
,
Nov 11 2016
Yep.
,
Dec 14 2016
,
Mar 9 2017
,
Mar 14 2017
RTCRtpSender: https://crbug.com/700916 RTCRtpReceiver: https://crbug.com/701330
,
Mar 20 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by kjellander@chromium.org
, Sep 30 2016Labels: -Type-Bug Type-Feature
Status: Available (was: Untriaged)