- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 May 2020 16:32:16 +0000
- To: public-webrtc-logs@w3.org
> 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. @guidou I think the web compat question here is did Chrome ever used to require ```js <iframe allow="camera; microphone; speaker"> ``` ...in order for the site to change audio output during a WebRTC call? Or did this always suffice: ```js <iframe allow="camera; microphone"> ``` ? If we go back to requiring the former, what sites might break? -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-output/issues/91#issuecomment-635456967 using your GitHub account
Received on Thursday, 28 May 2020 16:32:17 UTC