- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Sun, 20 Mar 2022 21:17:55 +0000
- To: public-webrtc-logs@w3.org
Meeting minutes and video are available [here](https://www.w3.org/2011/04/webrtc/wiki/March_15_2022). As noted in the minutes, the high level question was whether this is something the browser should handle "under the covers" (e.g. via a whitelist) or something that the application should have control over. If the application has the ability to disable hardware acceleration, how does it know *when* to do so? Disabling *all* hw acceleration, or hw acceleration for a particular codec, may be a blunt instrument. If there is a bug in a particular codec and set of hardware, how does the application know whether it is running on that hardware? It would need to access information about the device which would also be useful for fingerprinting. That concern is not present with a whitelist. -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/98#issuecomment-1073350805 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 20 March 2022 21:17:56 UTC