Re: [webrtc-pc] Should the spec describe addStream/onaddstream as legacy API?

@foolip addStream is [literally](https://dxr.mozilla.org/mozilla-central/rev/f40e24f40b4c4556944c762d4764eace261297f5/dom/media/PeerConnection.js#1055) `stream.getTracks().forEach(t => this.addTrack(t, stream))`

In Gecko (and the spec) whatever streams a track belongs to is irrelevant to the relationship RTCPeerConnection projects to the remote end. In other words, the streams passed in to `addTrack` are used solely for their msids.

getLocalStreams() in Firefox sadly returns the streams passed in to addTrack, which is [wildly misleading](https://jsfiddle.net/jib1/5afyv3eu/) except in the typical configuration.

getRemoteStreams() is somewhat useful, though redundant.

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1125#issuecomment-294265922 using your GitHub account

Received on Saturday, 15 April 2017 02:10:11 UTC