IndexedDB storage set on a subdomain of a site not cleared by "Forget About This Site"
Categories
(Toolkit :: Data Sanitization, defect, P2)
Tracking
()
People
(Reporter: englehardt, Unassigned)
References
(Blocks 1 open bug)
Details
STR:
- In a fresh profile go to https://senglehardt.com/test/dfpi/first_and_third.html. This page sets a random value in storage ONLY IF no value already exists.
- Refresh the page, you should see messages that say "IndexedDB key foo already written, NOT overwriting..." in each iframe. Note the random value written to storage for the same-site, cross-origin iframe (test.senglehardt.com)
- Open the History manager, right click "senglehardt.com" and click "Forget About This Site".
- Refresh the page once more.
ER: All storage locations in the same-site, same-origin iframe (senglehardt.com) and same-site, cross-origin iframe (test.senglehardt.com)
AR: The indexedDB key in the test.senglehardt.com iframe is not reset, even though all other storage locations included in this test page are.
Also just so it's clear: this test page is meant for dfpi, but this reproduces without dfpi.
Comment 1•5 years ago
•
|
||
This is because we only clear subdomains for localStorage, specified by the parameter here: https://searchfox.org/mozilla-central/rev/a4d62e09a4c46aef918667fa759bf9ae898dc258/toolkit/components/cleardata/ClearDataService.jsm#561
Originally this was done to mirror the old behavior for clearing localStorage when switching to next-gen. Arguably localStorage was always doing it right and we should do the same for all quota data. That would also significantly simplify the code.
Comment 2•4 years ago
|
||
Tom, was this fixed by bug 1628240?
Comment 3•4 years ago
|
||
(In reply to Johann Hofmann [:johannh] from comment #2)
Tom, was this fixed by bug 1628240?
Yes, it should be fixed by bug 1628240 and I verify that on my Nightly build. Based on this, I am going to close this ticket and mark it as a dup of bug 1628240.
Hi Steven, could you check if the issue still exists for the latest Nightly? If so, please feel free to reopen this ticket. Thanks!
Reporter | ||
Comment 4•4 years ago
|
||
(In reply to Tom Tung [:tt, :ttung] from comment #3)
Hi Steven, could you check if the issue still exists for the latest Nightly? If so, please feel free to reopen this ticket. Thanks!
I've confirmed that this is fixed in the latest Nightly.
Updated•4 years ago
|
Description
•