- From: cowwoc <cowwoc@bbs.darktech.org>
- Date: Fri, 13 Jun 2014 10:08:42 -0400
- To: public-media-capture@w3.org
On 13/06/2014 4:49 AM, bugzilla@jessica.w3.org wrote: > https://www.w3.org/Bugs/Public/show_bug.cgi?id=22214 > > --- Comment #3 from Harald Alvestrand <harald@alvestrand.no> --- > Rough consensus from the mailing list discussion seems to be: > > - Stored permission is only given to HTTPS pages (previous consensus, just > repeating here for background) > - It is an UA choice whether permission is granted for one device, a class of > devices, or all devices. UI needs to make clear what is being granted. > - Non-stored permission to a device lasts only while a MediaStreamTrack with > the device as source exists. Enabling/disabling the track has no effect on > permissions. > - Non-stored permissions do not survive a page reload (since the MST objects > don't survive it either). > > These are a summary of the points on which I think the ML has rough consensus. I asked before but don't recall getting an answer: is the permission scope (for HTTPS) the same as the HTTPS certificate? Meaning, does it span multiple domains if the certificate does? Or is it for a single domain? Or is it unspecified? Gili
Received on Friday, 13 June 2014 14:10:07 UTC