- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Mon, 17 Apr 2017 17:37:09 +0000
- To: public-webrtc-logs@w3.org
The reason Chrome doesn't return any receivers is that since it uses "Plan B" SDP, each m= section could be used to receive 0 to N streams. So there's no way to tell how many receivers are needed before the remote description is set. To answer your questions: > Does the receivers track id change? No; the receiver already had a track before `setRemoteDescription`, so that would mean changing the ID of an existing track. > Does ontrack fire with a track that has track.id=remoterandomaudio? It would be with "randomA", but the event *would* be fired on setting the remote description. This issue is related: https://github.com/w3c/webrtc-pc/issues/1013 -- GitHub Notification of comment by taylor-b Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1128#issuecomment-294537176 using your GitHub account
Received on Monday, 17 April 2017 17:37:16 UTC