Re: [w3c/permissions] Permission absent context == persistent permission (#85)

This API has context for calls to functions like `query()`, `request()`, and `revoke()`: the current [environment settings object](https://html.spec.whatwg.org/multipage/webappapis.html#environment-settings-object). Saying that `query()` only refers to the persistent part of a permission like geolocation would break its use in libraries that could take advantage of the current tab having permission, even if there's no persistent permission. (There is, of course, the privacy issue #52, but we shouldn't split discussion of that.)

I believe the original intent of this spec was to deal with both temporary and persistent permissions. It doesn't do a great job of that yet, because of the description of a [single permission store](https://w3c.github.io/permissions/#permission-store), but I think that's fixable.

I do think we might want to rename this spec to just "Permissions": it defines the platform permission architecture in addition to an API, and other specs, like Media Capture, are likely to reference this one primarily to interact with that architecture, not because they want to use the API. It's a little like https://storage.spec.whatwg.org/ in that regard.

I'll leave this open for a day or two to let other people chime in, but I don't expect to take these suggestions.

---
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/issues/85#issuecomment-213101521