- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Mar 2019 20:58:07 +0000
- To: public-webrtc-logs@w3.org
Thanks @jan-ivar! I've run into a couple of bugs in Chrome [here](https://bugs.chromium.org/p/chromium/issues/detail?id=944821) I do not think that `SRD, then use replaceTrack on a sender` is an API we should promote. Also there seem to be some cases where addTrack works (when called after setRemoteDescription; this is covered by the reuse in the addTrack algorithm afaics). Quite oddly, calling addTransceiver and then having a remote description which matches the SendEncodings did not seem to match the existing transceiver either. Not an API I would like to see but its a case where we need to decide what to do. -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2147#issuecomment-477344752 using your GitHub account
Received on Wednesday, 27 March 2019 20:58:09 UTC