Skip to content

Commit

Permalink
permissiosn: Clarify that manifest member is IWA-specific (#58)
Browse files Browse the repository at this point in the history
  • Loading branch information
robbiemc authored Feb 19, 2025
1 parent 18bc736 commit 8d95a91
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion Permissions.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ There are two mechanisms to control permissions on the Web today: [Permissions](

It is a non-goal to automatically grant access to all permissions listed in the manifest – we want the user to remain in control of the app’s capabilities. Because of this, along with the fact that manifest restrictions represent a developer choice rather than a user choice, Permissions Policy is better suited as a mechanism to enforce these permission restrictions.

We propose adding a new `permissions_policy` field to the Web App Manifest spec, which would contain a [policy directive](https://www.w3.org/TR/permissions-policy-1/#policy-directive) that maps [policy-controlled features](https://www.w3.org/TR/permissions-policy-1/#policy-controlled-feature) to an allowlist of origins. This field would define the default Permissions Policy for all top-level frames in an Isolated Web App. The [default allowlist](https://www.w3.org/TR/permissions-policy-1/#default-allowlists) for all policy-controlled features in Isolated Web Apps should default to 'none', and can only be expanded through the new permissions_policy manifest field. Child frame Permission Policies would inherit from their parent frame as they do today.
We propose adding a new `permissions_policy` field as an Isolated Web App specific extension to the Web App Manifest spec, which would contain a [policy directive](https://www.w3.org/TR/permissions-policy-1/#policy-directive) that maps [policy-controlled features](https://www.w3.org/TR/permissions-policy-1/#policy-controlled-feature) to an allowlist of origins. This field would define the default Permissions Policy for all top-level frames in an Isolated Web App. The [default allowlist](https://www.w3.org/TR/permissions-policy-1/#default-allowlists) for all policy-controlled features in Isolated Web Apps should default to 'none', and can only be expanded through the new permissions_policy manifest field. Child frame Permission Policies would inherit from their parent frame as they do today.

```
"permissions_policy": {
Expand Down

0 comments on commit 8d95a91

Please sign in to comment.