W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > February 2019

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

From: youennf via GitHub <sysbot+gh@w3.org>
Date: Sat, 16 Feb 2019 02:54:18 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-464277171-1550285657-sysbot+gh@w3.org>
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 6.4.4.1.

-- 
GitHub Notification of comment by youennf
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2106#issuecomment-464277171 using your GitHub account
Received on Saturday, 16 February 2019 02:54:20 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 4 June 2019 15:32:55 UTC