W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > June 2020

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

From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
Date: Mon, 15 Jun 2020 07:43:40 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-638621471-1592207018-sysbot+gh@w3.org>
alvestrand has just created a new issue for https://github.com/w3c/webrtc-pc:

== RTCRtpSender.getCapabilities() may not return correct information in sync ==
Chrome has found a [case](https://bugs.chromium.org/p/chromium/issues/detail?id=1047994) where getCapabilities() is going to have issues with delivering correct capability information about codec availability synchronously.

The two immediately obvious workarounds are:

- Fail the call with a LATER error code (but since it's a static method, there's no place to fire a "later has arrived" event at)
- Change the signature to async

The latter would be preferable from an architectural viewpoint, but has some compatibility issues.


Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2539 using your GitHub account
Received on Monday, 15 June 2020 07:43:42 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:51 UTC