- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Fri, 05 May 2017 16:54:18 +0000
- To: public-webrtc-logs@w3.org
I believe that paragraph is just obsolete. I traced the history and it goes at least as far back as when we had `addStream`. PR to remove it here: https://github.com/w3c/webrtc-pc/pull/1168 > In the old model when you have a audio m-line and a video m-line and you renegotiate without video, the video tracks ended will be called even though there is no removestream. This still happens. But `removeTrack` doesn't cause the implementation to renegotiate without video; only `videoTransceiver.stop` does. > Consider the (somewhat hypothetical) case where a track was part of multiple streams and is removed from some streams. Well, assuming that setting the remote description removes the track from the correct streams (it doesn't right now), you'd be able to listen for the streams' `"removetrack"` event. -- GitHub Notification of comment by taylor-b Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1161#issuecomment-299517991 using your GitHub account
Received on Friday, 5 May 2017 16:54:24 UTC