- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Mon, 24 Apr 2017 18:54:11 +0000
- To: public-webrtc-logs@w3.org
@foolip The only thing that's different from Chrome's implementation of `addStream` and the shim from Jan-Ivar's comment is that we react to changes in the stream. For example: if I call `addStream` while a stream contains one track, then add a track, then call `createOffer`, the offer will represent two tracks. We should measure how often applications actually do this, but I don't anticipate it being very common. And the workaround in JS (once `addTrack` is available) would be simple. So I don't expect removing this behavior to be a problem. -- GitHub Notification of comment by taylor-b Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1125#issuecomment-296788876 using your GitHub account
Received on Monday, 24 April 2017 18:54:19 UTC