Re: [webrtc-pc] RTCRtpSender.getCapabilities() may not return correct information in sync (#2539)

@aboba Caching after this has already been obtained asynchronously by other APIs seems like a sensible optimization (and nothing would prevent you from returning a cached result in a promise immediately), but considering there is no requirement that the app invoke and await createOffer() prior to calling getCapabilities(), having this be synchronous doesn't make sense. I am not in favor of having one API throw an exception unless another API on a different interface is called first.

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

Received on Wednesday, 17 June 2020 08:55:03 UTC