Re: [webrtc-pc] Inconsistent setting of receiver.track.readyState violates Mediacapture (#1575) from Jan-Ivar Bruaroey via GitHub on 2019-02-13 (public-webrtc-logs@w3.org from February 2019)

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Wed, 13 Feb 2019 15:28:47 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-463242377-1550071725-sysbot+gh@w3.org>

I'll work on a long-overdue PR here. I think firing `ended` is an exception to https://github.com/w3c/webrtc-pc/issues/565 because the target is different, and we don't want to violate mediacapture/downstream expectations.

Sure, a workaround would be to always remember to do
```js
pc.getTransceivers().forEach(tc => tc.stop());
pc.close();
```
...but that seems like an API bug. `pc.close` already mimics `stop()` wrt its effect on the *other* side.

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

Received on Wednesday, 13 February 2019 15:28:48 UTC