- From: Adam Bergkvist <adam.bergkvist@ericsson.com>
- Date: Wed, 4 Jun 2014 07:15:57 +0200
- To: Martin Thomson <martin.thomson@gmail.com>, Harald Alvestrand <harald@alvestrand.no>
- CC: "public-media-capture@w3.org" <public-media-capture@w3.org>
On 2014-06-03 19:23, Martin Thomson wrote: > On 3 June 2014 07:57, Harald Alvestrand <harald@alvestrand.no> wrote: >> Now, if an HTTP app wants to support the flow >> >> 1) Pick a camera >> 2) Take a photo >> 3) Repeat from 1) or end >> >> he has to open up a random device, enumerate labels, show the camera list, >> open up the camera, and hang on to his random device till the end. > > I think that this case is one where the site can (and should) move to > HTTPS and persistent permissions. > > I'll also note that this flow, as described, doesn't work for > snapshots. I believe that persistent permissions are required to > access other cameras. I believe Harald's intention is to hold on to a camera to keep the permission to enumerate the labels of other cameras; not have "no prompt access" to them. If the user decides to use an other camera from the *in app* camera list, a gUM() with prompt is needed (using the deviceId constraint). >At least in Firefox, a one-off consent grant > doesn't allow the site to open other cameras. So if I give Firefox a persistent permission to use a specific camera, can it flip to any other camera connected to my machine at any time? I wouldn't expect that. /Adam
Received on Wednesday, 4 June 2014 05:16:28 UTC