- From: guidou via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 May 2020 07:32:18 +0000
- To: public-webrtc-logs@w3.org
Chrome has never implemented a speaker permission, understood to mean an explicit permission specifically for nondefault speakers. Chrome allows setSinkId to succeed if the microphone permission has previously been granted and fails otherwise. We have considered adding a speaker-only permission for setSinkId (to better support the non-communications cases that don't require a mic), but there has been little demand for it and an there have been concerns that an UI prompt just for speakers might be confusing to users since the default speaker does not require authorization. The speaker feature policy code that was written in Chrome was removed because there was no implementation of a speaker permission, no mention of it in this spec, and, since the microphone permission is currently used for setSinkId, the microphone policy should work too. -- GitHub Notification of comment by guidou Please view or discuss this issue at https://github.com/w3c/mediacapture-output/issues/91#issuecomment-631292899 using your GitHub account
Received on Wednesday, 20 May 2020 07:32:20 UTC