- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Tue, 02 Jan 2018 10:41:24 +0000
- To: public-webrtc-logs@w3.org
> Are there strong reasons why we would change `replaceTrack`? No, feel free to close this. I was concerned about mixing synchronous and asynchronous operations yielding surprising results, but this is well-defined and there is already precedence for it (e.g. most async operations and `pc.close()`). This does expose another example of how Chromium does async operations incorrectly (https://crbug.com/webrtc/8692) but that needs to be addressed regardless. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1677#issuecomment-354739852 using your GitHub account
Received on Tuesday, 2 January 2018 10:41:26 UTC