- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Feb 2020 18:34:38 +0000
- To: public-webrtc-logs@w3.org
@jan-ivar I have interpreted this advice as referring to the potential for configuring the supported codec configurations. For example, if there is a flag to enable hardware acceleration, then if the flag is not set, higher profiles may not be provided by `getCapabilities` or 'createOffer', effectively hiding information on acceleration hardware from the application. This is different from the browser hiding supported codec configurations from `getCapabilities` or 'createOffer', because in practice there is no easy way for an application to re-enable them. The application could attempt to discover which codec configurations were really supported by calling `setCodecPreferences` with additional entries added to the list returned by `getCapabilities`, hoping that it would not return an error. But this wouldn't really address privacy concerns, it just makes application development more complicated. -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2460#issuecomment-589779062 using your GitHub account
Received on Friday, 21 February 2020 18:34:41 UTC