- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Mon, 01 May 2017 18:21:31 +0000
- To: public-webrtc-logs@w3.org
@ibc Stream and track `id`s are [immutable](https://w3c.github.io/mediacapture-main/getusermedia.html#dom-mediastreamtrack-id). **TL;DR:** Can't have both early tracks and correlated `id`s. @taylor-b A `null` track is no longer early media. @fippo I think we're fine if SRD is called first. It's the other way around that hurts. A revisit of the compatibility cost of early-media transceivers at the virtual interim seems prudent, as the consequences weren't apparent to everyone the first time around it seems. Basically, it breaks `track.id` correlation. `stream.id` correlation can be saved I think, as the earliest JS learns of a remote stream is on firing the `track` event (provided we rid implementations of `getRemoteStreams()`!). -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1128#issuecomment-298393489 using your GitHub account
Received on Monday, 1 May 2017 18:21:38 UTC