W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > December 2022

[webrtc-pc] is addTrack(track, stream, stream) allowed? (#2803)

From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
Date: Fri, 02 Dec 2022 12:53:57 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-1472818479-1669985635-sysbot+gh@w3.org>
fippo has just created a new issue for https://github.com/w3c/webrtc-pc:

== is addTrack(track, stream, stream) allowed? ==
This came up while looking at how Chrome parses msid:

results in
* two identical a=msid lines being generated
* In Chrome ontrack being called with two MediaStreams which are not identical. In Firefox only one MediaStream is generated

My interpretation of https://www.rfc-editor.org/rfc/rfc8830.html#section-3.2.2 is that the parsing is not valid.

has a step saying
For each stream in streams, add stream.id to [[[AssociatedMediaStreamIds]]](https://w3c.github.io/webrtc-pc/#dfn-associatedmediastreamids) *if it's not already there*

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2803 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 2 December 2022 12:53:59 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:59 UTC