- From: cowwoc <cowwoc@bbs.darktech.org>
- Date: Wed, 14 May 2014 12:10:04 -0400
- To: public-media-capture@w3.org
On 14/05/2014 8:49 AM, Harald Alvestrand wrote: > On 03/19/2014 03:34 PM, bugzilla@jessica.w3.org wrote: >> https://www.w3.org/Bugs/Public/show_bug.cgi?id=22214 >> >> Harald Alvestrand <harald@alvestrand.no> changed: >> >> What |Removed |Added >> ---------------------------------------------------------------------------- >> >> CC| |harald@alvestrand.no >> >> --- Comment #1 from Harald Alvestrand <harald@alvestrand.no> --- >> I suggest that this should be addressed in section 10.5 "Implementation >> Suggestions". >> >> I think the right properties to suggest are: >> >> - Permissions are given for a particular site (= origin) >> - Permissions persist at least until the page is closed or navigated >> away from >> - Users may allow permissions to persist longer (stored permissions) >> - Users may revoke permissions at any time >> >> I think it's an UA design choice whether permission is given for a >> particular >> camera or for all cameras. >> > This proposal has been hanging about for 2 months without comment. > > Should we consider it resolved, or do we need it on Monday's agenda? I'd like to propose an amendment. Since you've tied persistent permissions to HTTPS, how about remembering permissions across the same context as the certificate as opposed to just across a single host? Meaning, if the certificate spans sub-domains, the permission should too. Gili
Received on Wednesday, 14 May 2014 16:10:33 UTC