- From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
- Date: Tue, 3 Jun 2014 17:14:54 +0000
- To: Harald Alvestrand <harald@alvestrand.no>, "public-media-capture@w3.org" <public-media-capture@w3.org>
On 03/06/14 16:58, Harald Alvestrand wrote: > I'm starting to think that dropping permissions for http users as early > as possible is a reasonable thing to do..... I do have one outstanding > problem, which is the device enumeration and the hidden labels. > > We decided long ago that: > > a) we don't want to expose device labels to the drive-by web > b) we don't want a separate permissions prompt for getting device labels > c) we're OK with exposing device labels to anyone who's already grabbed > a device (which means that he's either passed a prompt or has a stored > permission). > > 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. Something escapes me here. Would not the app ask the user to select the camera the user would like to use to take the photo; the user is presented with a list of all cameras and selects (here the browser helps by presenting a view of what each camera "sees", or a label, or something). (I assumed no constraints used so any camera would do). The user picks a camera, hopefully the best suited, the app remembers the Id, and can next time ask for that camera.
Received on Tuesday, 3 June 2014 17:15:25 UTC