Re: [webrtc-pc] Recycling an m= section may not remove the old transceiver's remote track from its stream

Compare the above to:
```js
pc1.getTransceivers()[0].direction = "inactive";
await pc1.setLocalDescription(await pc1.createOffer());
await pc2.setRemoteDescription(pc1.localDescription);
await pc2.setLocalDescription(await pc2.createAnswer());
await pc1.setRemoteDescription(pc2.localDescription);
```
Which in Firefox [produces](https://jsfiddle.net/jib1/qemnx1ud/):
```
pc2's track removed
pc2's remote track muted
pc1's track removed
pc1's remote track muted
```
> "only remote descriptions change remote tracks/streams."

We could say that, but is it intuitive? What does that mean to "reject" if incoming media has already been announced?

Perhaps firing events in SRD(offer) is too soon? 

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

Received on Thursday, 8 March 2018 04:44:29 UTC