- From: Dan Jenkins via GitHub <sysbot+gh@w3.org>
- Date: Tue, 22 Mar 2022 14:57:01 +0000
- To: public-webrtc-logs@w3.org
I don't believe a whitelist makes sense across multiple browser vendors, developers are already having to write "if safari and 15.1... disable h264" kinds of conditions.... I like @fippo 's idea of "an emergency scenario API" that doesn't give fine grained control but does give the control to the end developer allowing them to do "if chrome 100 disable hardware acceleration" - at the end of the day developers are currently stopped from being able to fix a failing web app and sometimes spend weeks waiting for a browser release - why would a whitelist get changed any quicker - we're still reliant on someone from a browser agreeing the issue exists and removing something from a whitelist. Let the developer take control but do it in a way that doesn't allow fingerprinting. -- GitHub Notification of comment by danjenkins Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/98#issuecomment-1075287999 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 22 March 2022 14:57:06 UTC