- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 May 2017 19:39:09 +0000
- To: public-webrtc-logs@w3.org
Though when SRD is ***not*** called first, nothing protects the implicit receiver.track.id (created by the local UA's UUIDs algorithm) from colliding with future tracks renegotiated where SRD ***is*** called first. Though I'd file that under rare. > It's not intuitive. But when you add a track, you also automatically offer to receive a track, since you offer a sendrecv m= section. @taylor-b Which step in addTrack sets transceiver.direction to "sendrecv"? I don't see it, and direction doesn't appear to be intitialized anywhere or have a default value. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1128#issuecomment-300895501 using your GitHub account
Received on Thursday, 11 May 2017 19:39:17 UTC