- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 May 2020 15:45:54 +0000
- To: public-webrtc-logs@w3.org
> The latter. Accessing a user's _non-default_ speakers is a "powerful feature", and would be OFF in iframes by default. Right, this makes sense in the context of the audio output spec, but in general, the name is misleading to me. Allowing or not camera/microphone access is probably something much more easy to decide than allowing or not access to non-default speakers. As a web developer, what are the guidelines to allow/disallow 'speaker' selection? What am I trying to protect the user from? > A "speaker use" permission defaulting to OFF in iframes wouldn't be web compatible, so that's a different thing. Most people have some default audio output, and there's "Block Autoplay" for that. Sure, I was meaning a feature policy which would be ON by default and pages could explicitly set it to off. > To the page being iframed, I don't see much difference, since that seems easy to work around, as I mention in [#87 (comment)](https://github.com/w3c/mediacapture-output/issues/87#issuecomment-631521457). I was thinking of third-party iframes. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-output/issues/91#issuecomment-631558831 using your GitHub account
Received on Wednesday, 20 May 2020 15:45:56 UTC