Re: [w3c/permissions] Move permissions out to each spec (#263)

> @marcoscaceres Somewhat related to this, should web-share be listed as a permission in the spec? I ask because there appears to be a 1:1 mapping to the Permission Policy definitions for most permissions and permission policy settings.

No, and I totally understand that it looks like there is a 1:1 mapping. This is something I'm actually trying to fix.

This spec will only deal with APIs that prompt for UI: like Geolocation.  

I added some text to try to explain the relationship between the two specs:
https://w3c.github.io/permissions/#relationship-to-permissions-policy

For the case of "web-share", there is no permission prompt UI in any browser - hence, it's not part of this spec.  

> It isn't totally clear what the mapping "should" be (to me). Is the following correct?

 * permissions control what options are offered to users via the browser settings or GUI when you try to use an API.

Yes, what we call "power features" in our spec. Powerful features (e.g., geolocation) need to get "permission" via some UI.

> permission policy determines what the server thinks you should be able to use, and generally might be what sets the permission or what makes it visible to a user.

Correct (I wish Permissions Policy wouldn't of changed their name - it's made everything very confusing!)...

A "permissions" per the Permission Policy spec control the availability of an API in a given context, for example:

```HTML
<!-- this allows geolocation -->
<iframe allow="geolocation" src="https://third-party.com"></iframe>
```  

> Further, more closely related, if you move the permissions out to specs it would be really helpful to provide some information about where they are going to. Then we can update the browser compatibility info https://developer.mozilla.org/en-US/docs/Web/API/Permissions_API#browser_compatibility with spec links.

Sure! should I ping you directly? I can add something to our pull request template.  


-- 
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/263#issuecomment-906919210