Re: [w3c/permissions] Describe the permission store using constraints instead of a full model. (#96)

@alvestrand "Permission entries for a PermissionName are instances of that PermissionName's [permission entry type](https://api.csswg.org/bikeshed/?url=https://raw.githubusercontent.com/jyasskin/permissions/set-permission-store/index.bs#permission-entry-type), which will be PermissionStorageEntry [which is just a name] or **one of its subtypes**." It's up to the 'microphone' spec to define what data it needs in order to identify a microphone. You'll be able to look at the [Bluetooth spec](https://webbluetoothcg.github.io/web-bluetooth/#dictdef-bluetoothpermissionstorage) for how to do this, although it's not updated for this patch yet.

Realms are used in https://html.spec.whatwg.org/multipage/webappapis.html#realms-settings-objects-global-objects, and increasingly across the whole HTML spec. They're 1-1 with global objects and settings objects, which are per-frame rather than per-top-level-browsing-context. Because not all browsers and permissions work by top-level-browsing-context, I can't tie the base spec to those, but one of the extra constraints the media specs add can be that an iframe's realm should only get permission entries that were added by other realms with the same origin & top-level-origin.

---
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/96#issuecomment-218652922