Re: [w3c/permissions] Allow UAs to maintain zero or multiple permission stores. (#95)

> The storage model is a little wonky here. The key to the store is the name, rather than the name and the full descriptor. That means I can't give a site access to one specific camera, I have to store permissions for ALL cameras. I'm sure that's just a mistake, or it's being addressed elsewhere, but it seems like a very important condition.

@martinthomson It's being addressed in #91: we can't use the descriptor as the key because descriptors are information on searching for a particular capability, rather than the capability itself. For example, [`MediaTrackConstraints`](https://w3c.github.io/mediacapture-main/#idl-def-MediaTrackConstraints) has all sorts of attributes of the camera or mic, but we'd only store the camera or mic id in the permission store. "push" and "midi" (#90), on the other hand, have a lattice structure on their permissions, where requesting `{name:'push',userVisibleOnly:false}` should imply getting `{name:'push',userVisibleOnly:true}`, and again storing the descriptor would do the wrong thing.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/permissions/pull/95#issuecomment-215747093