- From: Harald Alvestrand <harald@alvestrand.no>
- Date: Wed, 08 Jul 2015 00:00:21 +0200
- To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Jan-Ivar Bruaroey <jib@mozilla.com>
- CC: public-media-capture@w3.org
Den 07. juli 2015 23:06, skrev Silvia Pfeiffer:
>
> On 7 Jul 2015 6:52 am, "Jan-Ivar Bruaroey" <jib@mozilla.com
> <mailto:jib@mozilla.com>> wrote:
>>
>> On 7/6/15 4:00 PM, Harald Alvestrand wrote:
>>>
>>> I am somewhat confused by one thing, though....
>>>
>>> If I do:
>>>
>>>
>>> enumerateDevices() => { device: id = 12345 type = videoinput }
>>>
>>> getUserMedia({video: { deviceId: { exact: 12345 } }
>>>
>>> enumerateDevices()
>>>
>>> am I guaranteed that the device with id 12345 in the second
>>> enumerateDevices is the same device as the one I grabbed?
>>
>>
>> OK so we need to be clearer about what persisting means. I meant persist (to disk) across browser sessions, leaving deviceIds stable "for the current session", by which I meant browser session, i.e. until you quit the browser.
>
> I think it needs to persist longer than that. It should persist until
> the OS can't associate it any longer.
>
> Here's a use case: set up Google chrome in kiosk mode (e.g. for a kiosk
> at an airport), run a video conference app on it that has two video
> cameras, e.g. face & document. You only want to have to associate device
> ids once, when you set up the hardware. Then store it to localStorage
> and reuse after every reboot.
In kiosk mode locked down to a video conferencing application, I would
expect persistent permission to be granted during the setup process.
But there might be a subtlety I'm not seeing...
Received on Tuesday, 7 July 2015 22:00:52 UTC