Open
Bug 1531012
(permissions-policy)
Opened 7 years ago
Updated 2 days ago
[meta] Permissions Policy tracking
Categories
(Core :: DOM: Security, task, P3)
Core
DOM: Security
Tracking
()
NEW
People
(Reporter: annevk, Unassigned)
References
(Depends on 22 open bugs, )
Details
(Keywords: meta, parity-chrome, web-feature)
User Story
web-feature: permissions-policy
As detailed somewhat in https://github.com/w3c/webappsec-feature-policy/issues/282 Mozilla has some reservations on the current Feature Policy setup. Until we have an agreed upon way forward we should probably not invest too much engineering time into Feature Policy.
Given that we do have an implementation, this issue exists to track the various bugs with that as well as feature requests we've gotten, to enable us to make decisions that take all the various pieces into account.
Updated•7 years ago
|
Summary: Feature Policy tracking → [meta] Feature Policy tracking
| Assignee | ||
Updated•7 years ago
|
Component: DOM → DOM: Core & HTML
Updated•7 years ago
|
Assignee: nobody → tnguyen
Updated•7 years ago
|
Assignee: tnguyen → nobody
Depends on: 1641032
| Reporter | ||
Updated•6 years ago
|
Alias: feature-policy → permissions-policy
Summary: [meta] Feature Policy tracking → [meta] Permissions Policy tracking
Updated•5 years ago
|
Depends on: permissions-policy-header
| Reporter | ||
Updated•4 years ago
|
Depends on: CVE-2022-29909
Updated•4 years ago
|
Depends on: CVE-2022-38473
Updated•4 years ago
|
Severity: normal → S3
Updated•3 years ago
|
Comment 1•1 year ago
|
||
Hello all,
What's the overall status of this project and timeline? (rough estimate is fine)
Updated•5 months ago
|
User Story: (updated)
Keywords: web-feature
Updated•5 months ago
|
Updated•4 months ago
|
Keywords: parity-chrome
Updated•2 months ago
|
Type: enhancement → task
Updated•1 month ago
|
Component: DOM: Core & HTML → DOM: Security
You need to log in
before you can comment on or make changes to this bug.
Description
•