- From: Jan-Ivar Bruaroey <jib@mozilla.com>
- Date: Tue, 07 Jul 2015 18:39:10 -0400
- To: Harald Alvestrand <harald@alvestrand.no>, Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- CC: public-media-capture@w3.org
On 7/7/15 6:00 PM, Harald Alvestrand wrote:
> 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.
Right, once permission has been granted (even once), then the id is
persisted until cookies are cleared. No worries.
I was talking about before permission has ever been granted to a site
(or after cookies have been cleared). Then the id is stable only until
the browser is closed (like in private browsing in Firefox).
.: Jan-Ivar :.
Received on Tuesday, 7 July 2015 22:39:41 UTC