W3C home > Mailing lists > Public > public-media-capture-logs@w3.org > June 2016

Re: [mediacapture-main] MUST clear requirement for deviceId

From: stefan hakansson via GitHub <sysbot+gh@w3.org>
Date: Fri, 03 Jun 2016 11:25:04 +0000
To: public-media-capture-logs@w3.org
Message-ID: <issue_comment.created-223555048-1464953103-sysbot+gh@w3.org>
@ShijunS thanks for elaborating on the different parts here. I think 
you are definitely right in that more clarification is needed is 
needed in the spec. And we also need to agree on what behavior that is
 to be mandated by the spec.

As @jan-ivar and @alvestrand points out, one intention was to enable a
 site (even if it did not request or the user/browser did not  approve
 _persisted_ access to microphone(s)/camera(s)) to find out if a 
preferred device is connected, and if so request it. It was also 
intended that clearing cookies would reset this (and the spec should 
be clearer). This behavior would be useful for sites (and end users) 
if they do not have persisted access to use input devices.

We could remove this if the default will be that browsers persist 
access to input devices by default. It would simplify since the 
options are fewer, either the site does neither have access to input 
devices nor stable deviceIds, or it has access and stable deviceIds. 
It would also make it clearer to the end user: if there is persisted 
rights to use camera and mike the issue of fingerprinting is probably 
less important, and if there is not persisted rights we have not added
 a big fingerprint.

The problem with removing would IMO be that we remove the possibility 
for some middle ground: the site can ask for the "right" devices, but 
the user must approve every time. And also for the case @jan-ivar 
mentions: the user can revoke persisted permissions, but the site can 
ask for the "right" devices next time.

I'm not sure how important those cases are, but this was a background 
to why the spec say what it says.

GitHub Notification of comment by stefhak
Please view or discuss this issue at 
 using your GitHub account
Received on Friday, 3 June 2016 11:25:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:27:29 UTC