Open
Bug 1628313
Opened 4 years ago
Updated 2 years ago
Delete third-party storage after Storage Access API transition
Categories
(Toolkit :: Data Sanitization, task, P3)
Toolkit
Data Sanitization
Tracking
()
NEW
People
(Reporter: annevk, Assigned: baku)
References
(Blocks 1 open bug)
Details
After a Storage Access API transition from non-blocked-third-party storage to first-party storage we should make sure to clean the old storage so it's not accessible in future sessions (e.g., if the transition got reversed somehow).
Updated•4 years ago
|
Type: defect → task
Priority: -- → P2
Comment 1•4 years ago
|
||
That seems more complicated than it sounds though, what if other iframes had access to that storage at the same time?
Reporter | ||
Comment 2•4 years ago
|
||
That's a very good point. I suppose we need to mark it in some way and clear it when nobody has an "active" reference. At the latest this will be upon browser restart. If the transition got reversed before that point we should probably still clear it.
Updated•4 years ago
|
Blocks: DynamicFirstPartyIsolation
Updated•2 years ago
|
Severity: normal → N/A
Priority: P2 → P3
You need to log in
before you can comment on or make changes to this bug.
Description
•