Standardize or remove RTCPeerConnection#addStream/removeStream and related events |
|||||||||||
Issue descriptionhttps://jsbin.com/qirujiq/edit?html,output tests for the existence of addStream, removeStream, onaddstream, onremovestream, getLocalStreams, getRemoteStreams and the MediaStreamEvent interface. Blink and Edge have all of them. Gecko has all except removeStream: https://github.com/mozilla/gecko-dev/blob/master/dom/webidl/RTCPeerConnection.webidl WebKit has all except onremovestream: https://github.com/WebKit/webkit/blob/master/Source/WebCore/Modules/mediastream/RTCPeerConnection.idl Use counters: https://www.chromestatus.com/metrics/feature/timeline/popularity/1641 https://www.chromestatus.com/metrics/feature/timeline/popularity/1643 https://www.chromestatus.com/metrics/feature/timeline/popularity/1644 https://www.chromestatus.com/metrics/feature/timeline/popularity/1646
,
Mar 3 2017
guidou@, in order to remove this, which bits of https://w3c.github.io/webrtc-pc/#rtcpeerconnection-interface-extensions would we have to ship first? Just addTrack and removeTrack? Is there a bug for that which we could mark as blocking this?
,
Mar 6 2017
,
Mar 6 2017
,
Mar 9 2017
,
Mar 29 2017
,
Mar 29 2017
The spec has moved away from streams, and RTP Media API (RTCRtpSender and RTCRtpReceiver stuff) works with tracks. Use of streams should be deprecated.
,
Mar 29 2017
... or implemented as "for (track in stream) add/removeTrack" and addStream/removeStream added to the standard as a legacy API due to its existing browser support.
,
Apr 11 2017
,
Apr 14 2017
,
Apr 14 2017
,
Mar 3 2018
,
Jun 21 2018
,
Jun 21 2018
,
Sep 4
The decision is to deprecate and remove them, but they're too heavily used. This bug is non-actionable for the foreseeable future. |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by guidou@chromium.org
, Feb 28 2017