Manage storage principal in parent process
Categories
(Core :: Privacy: Anti-Tracking, enhancement)
Tracking
()
People
(Reporter: farre, Unassigned)
Details
The syncing of principals in general and the storage principal in particular should be handled from the parent, either by computing the storage principal in the parent or handling principals initilalization entirely in the parent.
Shouldn't this ticket belong to the Privacy: Anti-Tracking component? At least I don't see why this should belong to DOM: Core & HTML.
|
Reporter | |
Comment 2•5 years ago
|
||
Sure, I'll move it.
|
||
Comment 3•1 month ago
|
||
:farre, I read this as a general fission placeholder; are there specific architectural changes you had envisioned for this or could it make sense to resolve this fixed/wfm/duped given that we have principal validation and plans like bug 1853706 (and related work to support it) to clean things up to be more of a chain-of-authorization where the principal / storagekey are inherent to the actor rather than transmitted and validated?
|
|
Reporter | |
Comment 4•1 month ago
|
||
I don't even remember what that was about. I think we can close this.
Description
•