- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Mar 2018 05:13:51 +0000
- To: public-webrtc-logs@w3.org
Found a clue in [an old version of the spec](https://w3c.github.io/webrtc-pc/archives/20150611/webrtc.html#dispatch-receiver) to why we fire at least the `track` event in SRD(offer): *"For the answerer, ontrack will continue to fire during setRemoteDescription, as it does today (this is necessary to allow the answerer to reject offered tracks by stopping them)"* -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1778#issuecomment-371381278 using your GitHub account
Received on Thursday, 8 March 2018 05:14:04 UTC