Closed
Bug 1968721
Opened 10 months ago
Closed 3 months ago
Storage-Access-Headers: Refactor frame storage access activation from bool to enum
Categories
(Core :: Privacy: Anti-Tracking, task, P3)
Core
Privacy: Anti-Tracking
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: manuel, Unassigned)
References
(Blocks 1 open bug)
Details
Currently we track it two separate booleans: (access, active),
Need to have this enum for request header:
- None (false, false)
- Inactive (true, false)
- Active (true, true)
|
||
Updated•9 months ago
|
Assignee: nobody → manuel
|
Reporter | |
Updated•9 months ago
|
Status: NEW → ASSIGNED
|
|
Reporter | |
Comment 1•8 months ago
|
||
Different refactor necessary. Will revisit at later stage of project.
Assignee: manuel → nobody
Status: ASSIGNED → NEW
Priority: P2 → P3
|
|
Reporter | |
Comment 2•3 months ago
|
||
The refactor isn't necessary anymore, because the sticky part of the storage-access-headers wasn't finalized (privacycg/storage-access-headers#6, privacycg/storage-access-headers#22).
We can reconsider if we pick up work on storage-access-headers and the sticky behavior becomes part of the spec.
Status: NEW → RESOLVED
Closed: 3 months ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•