Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions features/draft/feature-policy.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
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
Comment thread
ddbeck marked this conversation as resolved.
Outdated
- api.HTMLIFrameElement.featurePolicy
12 changes: 12 additions & 0 deletions features/draft/feature-policy.yml.dist
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
# 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.HTMLIFrameElement.featurePolicy
8 changes: 8 additions & 0 deletions features/draft/permissions-policy.yml
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

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The 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
24 changes: 24 additions & 0 deletions features/draft/permissions-policy.yml.dist
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
4 changes: 4 additions & 0 deletions scripts/specs.ts
Original file line number Diff line number Diff line change
Expand Up @@ -104,6 +104,10 @@ const defaultAllowlist: allowlistItem[] = [
[
"https://www.w3.org/TR/DOM-Level-2-Style/",
"Allowed because the css-object-model-discouraged feature points to it."
],
[
"https://www.w3.org/TR/2019/WD-feature-policy-1-20190416/",
"Allowed because feature policy was replaced by permissions policy."
]
];

Expand Down