Re: [webrtc-pc] transceiver.stop() shouldn't block in-progress replaceTrack from succeeding (#2106)

I know this is an existing practice for RTCPeerConnection but it does not seem like a good pattern for an API to return a promise and never reject/resolve it. That may leave code to be hanging forever due to some timing issues.
I would just remove step

GitHub Notification of comment by youennf
Please view or discuss this issue at using your GitHub account

Received on Saturday, 16 February 2019 02:54:20 UTC