Complete RTCRtpReceiver in JavaScript |
|||||||||||
Issue descriptionSpec: - RTCRtpReceiver https://w3c.github.io/webrtc-pc/#rtcrtpreceiver-interface - RTCPeerConnection extensions https://w3c.github.io/webrtc-pc/#rtcpeerconnection-interface-extensions WebRTC repo interface: https://cs.chromium.org/chromium/src/third_party/webrtc/api/rtpreceiverinterface.h
,
Mar 20 2017
,
Mar 28 2017
,
Mar 28 2017
,
Apr 12 2017
This has been exposed now, see https://bugs.chromium.org/p/chromium/issues/detail?id=703122: interface RTCRtpReceiver { readonly attribute MediaStreamTrack track; sequence<RTCRtpContributingSource> getContributingSources(); }; interface RTCRtpContributingSource { readonly attribute DOMHighResTimeStamp timestamp; readonly attribute unsigned long source; }; This bug is to implement the rest of RTCRtpReceiver.
,
Apr 24 2017
Bumping to M60. Please correct if that's wrong.
,
Apr 25 2017
*holler* this is in M59.
,
Apr 25 2017
Updated summary to reflect that this bug tracks more than just what was exposed in M59.
,
Jun 12 2017
If a remote track is removed we need the track.onended to fire? See https://github.com/w3c/webrtc-pc/issues/1182#issuecomment-304165072 and referenced discussions.
,
Jan 8
,
Jan 8
,
Jan 8
,
Jan 10
|
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by hbos@chromium.org
, Mar 14 2017