- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Apr 2018 23:02:26 +0000
- To: public-webrtc-logs@w3.org
> With this change we'd be firing not just ended, but also muted on remote tracks, as well as removing them from any remote streams and firingremovetrack on said streams. Is that the intent? Yes. The intent is that there should be no observable difference between `setRemoteDescription(rejected_sendrecv_answer)` and `setRemoteDescription(rejected_inactive_answer)`. > Also, if we we want to do this, I think it would make sense to preserve the symmetry of doing this on the offerer side as well. Currently, this is done in prose under [stop()](http://w3c.github.io/webrtc-pc/#dom-rtcrtptransceiver-stop): > > * *" In addition, since the receiver's [[ReceiverTrack]] has ended, the steps described in track ended MUST be followed."* > > We probably want to extend this to do `muted` and `removetrack` then too, right? So, you're suggesting to do the `muted` and `removetrack` in the `stop()` steps, rather than `setRemoteDescription` steps? That would also resolve #1178. So that seems ok by me. I'll make another PR for that. -- GitHub Notification of comment by taylor-b Please view or discuss this issue at https://github.com/w3c/webrtc-pc/pull/1845#issuecomment-384460501 using your GitHub account
Received on Wednesday, 25 April 2018 23:02:31 UTC