-
Notifications
You must be signed in to change notification settings - Fork 145
Add features for permissions policy and feature policy #2661
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
draft_date: 2025-02-16 | ||
name: Feature policy | ||
description: The `Feature-Policy` response header sets whether a policy-controlled feature, such as an API, may be used in a document. Not to be confused with permissions policy. | ||
spec: https://www.w3.org/TR/2019/WD-feature-policy-1-20190416/ | ||
caniuse: feature-policy | ||
discouraged: | ||
according_to: | ||
- https://github.com/w3c/webappsec-permissions-policy/pull/379 | ||
alternatives: | ||
- permissions-policy | ||
compat_features: | ||
- api.Document.featurePolicy | ||
- api.FeaturePolicy | ||
- api.FeaturePolicy.allowedFeatures | ||
- api.FeaturePolicy.allowsFeature | ||
- api.FeaturePolicy.features | ||
- api.FeaturePolicy.getAllowlistForFeature | ||
- api.HTMLIFrameElement.featurePolicy |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
# Generated from: feature-policy.yml | ||
# Do not edit this file by hand. Edit the source file instead! | ||
|
||
status: | ||
baseline: false | ||
support: | ||
chrome: "74" | ||
chrome_android: "74" | ||
edge: "79" | ||
compat_features: | ||
- api.Document.featurePolicy | ||
- api.FeaturePolicy | ||
- api.FeaturePolicy.allowedFeatures | ||
- api.FeaturePolicy.allowsFeature | ||
- api.FeaturePolicy.features | ||
- api.FeaturePolicy.getAllowlistForFeature | ||
- api.HTMLIFrameElement.featurePolicy |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
draft_date: 2025-02-16 | ||
name: Permissions policy | ||
description: The `Permissions-Policy` response header sets whether a policy-controlled feature, such as an API, may be used in a document. | ||
spec: https://w3c.github.io/webappsec-permissions-policy/ | ||
caniuse: permissions-policy | ||
compat_features: | ||
- http.headers.Permissions-Policy | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I guess none of https://w3c.github.io/webappsec-permissions-policy/#idl-index has shipped... There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah. I asked about this at the time and it seems like at some point somebody thought about it but nothing else came of it. |
||
- http.headers.Permissions-Policy.wildcards |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
# Generated from: permissions-policy.yml | ||
# Do not edit this file by hand. Edit the source file instead! | ||
|
||
status: | ||
baseline: false | ||
support: | ||
chrome: "108" | ||
chrome_android: "108" | ||
edge: "108" | ||
compat_features: | ||
# baseline: false | ||
# support: | ||
# chrome: "88" | ||
# chrome_android: "88" | ||
# edge: "88" | ||
- http.headers.Permissions-Policy | ||
|
||
# ⬇️ Same status as overall feature ⬇️ | ||
# baseline: false | ||
# support: | ||
# chrome: "108" | ||
# chrome_android: "108" | ||
# edge: "108" | ||
- http.headers.Permissions-Policy.wildcards |
Uh oh!
There was an error while loading. Please reload this page.