- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Tue, 12 Sep 2017 00:36:27 +0000
- To: public-webrtc-logs@w3.org
@fluffy The PR includes this note that tries to explain why the attribute exists: > If a transceiver is created by a method other than setRemoteDescription, receiver.track.id will be set to a randomly generated value instead of one that comes from SDP. So, this attribute can be used to access the track ID from SDP when it differs from the randomly generated ID that was decided beforehand. In case the application cares about signaled track IDs. Do you have any suggestions for how to clarify this? -- GitHub Notification of comment by taylor-b Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1588#issuecomment-328697042 using your GitHub account
Received on Tuesday, 12 September 2017 00:36:22 UTC