Rename all the things #379
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
foolip
added a commit
to whatwg/fullscreen
that referenced
this pull request
Jun 29, 2020
foolip
added a commit
to whatwg/fullscreen
that referenced
this pull request
Jun 29, 2020
pull bot
pushed a commit
to Yannic/chromium
that referenced
this pull request
Jun 30, 2020
Add flags for the work of renaming Feature Policy as Permissions Policy The rename discussion was at w3c/webappsec-permissions-policy#359. The PR that made the actual changes was w3c/webappsec-permissions-policy#379 committed as w3c/webappsec-permissions-policy@14898d1. Enable this in Chrome with --enable-features=PermissionsPolicyHeader Bug: 1095641 Change-Id: Iccb6114bfeddb219e2cfe1a788d530dbcd8ba179 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2246870 Reviewed-by: Ian Clelland <iclelland@chromium.org> Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Commit-Queue: Charlie Hu <chenleihu@google.com> Cr-Commit-Position: refs/heads/master@{#783959}
xfq
added a commit
to w3c/web-roadmaps
that referenced
this pull request
Jul 23, 2020
This was referenced Jul 23, 2020
|
Given all the open issues for fixing other specs based on this rename: This change renames the header as well, which seems to be a breaking change. Should we just be applying the rename and implicitly implementing this behavior for both headers? WebXR, for example, already has people using |
Bahanix
added a commit
to Bahanix/rails
that referenced
this pull request
Nov 14, 2020
HTTP Feature-Policy has been renamed to Permissions-Policy: * Original issue: w3c/webappsec-permissions-policy#359 * PR: w3c/webappsec-permissions-policy#379 * Doc: https://w3c.github.io/webappsec-permissions-policy/ Mozilla documentation has been updated on July 2020: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Feature-Policy
fxn
pushed a commit
to rails/rails
that referenced
this pull request
Nov 18, 2020
HTTP Feature-Policy has been renamed to Permissions-Policy: * Original issue: w3c/webappsec-permissions-policy#359 * PR: w3c/webappsec-permissions-policy#379 * Doc: https://w3c.github.io/webappsec-permissions-policy/ Mozilla documentation has been updated on July 2020: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Feature-Policy
This was referenced Mar 12, 2021
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
This change renames "Feature Policy", and all associated concepts, interfaces and APIs, to "Permissions Policy".
Closes: #359