- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Mon, 29 Mar 2021 23:50:05 +0000
- To: public-webrtc-logs@w3.org
> You seem to have a special case new situation where you want user activation required both for showing the permission request, and then using the resulted granted permission afterward. It's not a special case, but one that arises naturally from connecting a source that requires transient activation to obtain, to a sink that requires [autoplay](https://developer.mozilla.org/en-US/docs/Web/Media/Autoplay_guide#autoplay_availability). The latter isn't standardized, so we don't have a way to define interactions with it. > > ... getDisplayMedia, as well as getUserMedia ... > > Maybe, if those things also require a second user activation to start playing the media. I'd be surprised if they did; I suspect that if the user has granted you screen sharing or video call permissions or whatever, that the browser isn't going to need a further user activation restriction on actually using those. Yes, all browsers appear to waive needing to click on the page to play audio if the page has been granted camera or microphone permission. But it's not written down anywhere, and it's not obvious (it lets me play [any sound](https://jan-ivar.github.io/dummy/gum_audio_tone.html), not just "those"). Since users shouldn't need to grant mic permission to switch speaker outputs, this spec defines a new in-browser picker API that requires transient activation to invoke, that is trying to say that autoplay must work afterwards. We don't know if autoplay is sticky, and we don't know whether the [transient activation duration](https://html.spec.whatwg.org/multipage/interaction.html#transient-activation-duration) is long enough for a user to have time to respond to a prompt. I suggest we remove the problematic sentence for now and leave a note about autoplay. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-output/pull/118#issuecomment-809799773 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 29 March 2021 23:50:06 UTC