W3C home > Mailing lists > Public > public-webrtc@w3.org > May 2017

[webrtc-pc] Stream IDs MUST be generated according to mediacapture-main, but webrtc-pc contradicts this

From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
Date: Wed, 10 May 2017 18:46:26 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-227774932-1494441985-sysbot+gh@w3.org>
taylor-b has just created a new issue for https://github.com/w3c/webrtc-pc:

== Stream IDs MUST be generated according to mediacapture-main, but webrtc-pc contradicts this ==
Comment from @Pehrsons on #1161:

>The current draft of mediacapture-main even says that stream ids `MUST` always be generated. It doesn't allow for the `id` to be transferred from the remote side as it does for `MediaStreamTrack`.
>
>Of course webrtc-pc contradicts this by saying
>> When a MediaStream is created to represent a stream obtained from a remote peer, the id attribute is initialized from information provided by the remote source. 

The relevant part of mediacapture-main is:

> When a MediaStream object is created, the User Agent must generate an identifier string, and must initialize the object's id attribute to that string.

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1196 using your GitHub account
Received on Wednesday, 10 May 2017 18:46:32 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:50 UTC