Re: [w3c/permissions] Only allow permissions.request() during user interaction (#77)

@jan-ivar says:

"""Example (today): Alice chats: "Hi Frank and Charlie, lets meet again at https://appear.in/alice"

Charlie uses Chrome, so his page loads right up and the call is on.
Frank uses Firefox, so Firefox asks him to share his camera. He agrees, and the call is on.
With your proposal, Charlie is unaffected, but Frank is now two clicks behind instead of one:

Frank uses Firefox, so he has to click a button for Firefox to ask him to share his camera. He agrees, and the call is on.
This seems undesirable."""

My goal is for the permission grant to be a seamless part of the workflow. Ideally, both Frank and Charlie would get an HTML page like:

```
Welcome to Video Conference Example App Dot Com!
[ Join Call with Alice ]
```

Clicking on the [ Join Call with Alice ] button is a gesture, and the onclick event handler is thus now empowered to do such things as call getUserMedia. A nice UA could then fulfill the getUserMedia call in its own way, e.g.

* Returning a descriptor to the device's 1 camera
* Showing a chooser to choose between the several cameras (say, front and back)
* Returning a descriptor to the device's front camera, but making it easy for the person to switch to the back camera (e.g. by detecting device rotation, showing a Switch Camera button in a semi-transparent overlay, or whatever else)

I really don't see automatic, gesture-less camera/mic enablement onload as a good idea, as a default experience.

Unless, and I've said this before in other fora, the UX offers a chooser like:

```
Select a camera and mic:
  __ Front Camera + Mic __
  Rear Camera + Mic
  Mic Only

[ Cancel ]    [[ Join Call ]]

   [x] Always use this choice with calls.example.com

```

If the person checks that Always Use checkbox, then I think that's a reasonable signal that the person wants to auto-join all calls on that site with the selected media input devices.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/permissions/issues/77#issuecomment-225063771