- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Sep 2019 19:39:30 +0000
- To: public-webrtc-logs@w3.org
The remaining issue in https://github.com/w3c/webrtc-pc/issues/1575#issuecomment-463242377 required a PR, so I added one. With this merged, we'll have the following spec behavior (with a running loop as starting point): Method | Event fired on `pc2.getTransceivers()[0].receiver.track` ------------ | ------------- pc1.close() | `mute`¹ pc1.getTransceivers()[0].stop() | `mute`¹, followed by `ended` on renegotiation pc2.close() | `ended` (this PR https://github.com/w3c/webrtc-pc/pull/2296) pc2.getTransceivers()[0].stop() | `ended` pc1.getTransceivers()[0].sender.track .stop() | ² pc2.getTransceivers()[0].receiver.track .stop() | --- <sub>1. Chrome and [Firefox](https://bugzilla.mozilla.org/show_bug.cgi?id=1545855) have bugs where they don't fire `mute` on receiving RTCP BYE, which the spec says they must.</sub> <sub>2. [Chrome](https://bugs.chromium.org/p/chromium/issues/detail?id=941740) has a bug here where it fires `mute` when it shouldn't. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1575#issuecomment-530534131 using your GitHub account
Received on Wednesday, 11 September 2019 19:39:32 UTC