- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Nov 2020 14:59:54 +0000
- To: public-webrtc-logs@w3.org
henbos has just submitted a new pull request for https://github.com/w3c/webrtc-pc: == Allow piggybacking getCapabilities on most recent offer or answer == Fixes #2460. While the fingerprint note previously already said the capabilities returned could be a subset of the real capabilities in privacy-sensitive contexts, this PR makes it clearer that this can be even more true prior to calling createOffer or createAnswer. This also resolves any synchronicity issues by allowing the result to be incomplete if the user agent doesn't know some capabilities yet (e.g. may require accessing hardware). This PR also makes the requirements of this API a little bit clearer by saying that after creating an offer or answer, the capabilities returned MUST match the SDP. This attempts to clarify two things: - Allow getCapabilities not to leak anything that we are not already leaking in createOffer. - By "piggybacking" on createOffer, we get around the limitations of this synchronous API by encouraging you to have already awaited an asynchronous API. See https://github.com/w3c/webrtc-pc/pull/2597 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 5 November 2020 14:59:56 UTC