Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
The
Feature-Policy
header changed toPermissions-Policy
some time ago. This PR addsPermission-Policy
BCD, keeping the existingFeature-Policy
data but classifying it as support under an alternative name.This is part of the work described at mdn/content#22347
See my research document at https://docs.google.com/document/d/14xHANU3n43PfJR_dCpEwVCiVYv12BAfGqOICNvd79R4/edit#heading=h.mahbkxhoku5t for a list of the
Permissions-Policy
directives I am intending to implement on MDN as part of this work. This gives us parity with what was previously documented underFeature-Policy
, but it adds a few more that are known to be supported, and it removes mention of some that were obviously being worked on at some point, but never seem to have gotten any traction.Note — I have not yet deleted the
Feature-Policy.json
file, so that the existing docs don't break if the new BCD is merged and imported sooner than the MDN content is updated. We can always delete that later on.Test results and supporting details
New information was largely gotten from https://github.com/w3c/webappsec-permissions-policy/blob/main/features.md.
Related issues