You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
So here's the problem in a nutshell that's been encountered by users numerous times (#211#347#952#1395#1427#1468 etc.)
deleting cookies of website X only on 1 container: works
deleting localStorage of website X only on 1 container: doesn't work, all containers deleted
bad workaround: disable localStorage cleaning entirely and never ever let the extension touch them :-(
better workaround: whitelist website X on all containers and not just 1
As far as I know this localStorage flaw also applies to the other storage types: Cache, IndexedDB, Plugin Data, Service workers... EXCEPT COOKIES which behave correctly. This is due to WebExtension API limitations as stated here #1395 (comment)
Describe the solution that you'd like
Until the Firefox devs implement it properly, some safeguards can be tried to limit that frustrating global cleanup:
SOLUTION 1: when container support is enabled, pressing the + Whitelist button should add the rule to ALL containers instead of just 1
SOLUTION 2: this was proposed by @SpaceClicker here and it's probably a more elegant solution #1427 (comment) basically add a check that goes something like this: if www.example.com localStorage whitelist rule exists in ANY container -> DO NOT cleanup
The idea is that if the user went out of his way to WHITELIST a website on 1 container, it's better user experience to be overcautious and let that data survive on all containers than it is to be too overzealous and delete that data on all containers.
The text was updated successfully, but these errors were encountered:
Currently, if I have LocalStorage Cleanup, I have a host allowed that still has its local storage cleaned up at a random time. I tried allowing the host in the default container, but it still happens.
I have to keep this setting disabled until the extension is fixed, but this doesn't block tracking using local storage on other websites.
It seems like I have another extension that removes my local storage, because even when LocalStorage Cleanup is disabled, my keys are still getting removed. Or CAD is misbehaving. I'll make more tests.
EDIT: I had Firefox set to remove offline data when it closes.
Acknowledgements
Is your feature request related to a problem? Please describe.
So here's the problem in a nutshell that's been encountered by users numerous times (#211 #347 #952 #1395 #1427 #1468 etc.)
As far as I know this localStorage flaw also applies to the other storage types: Cache, IndexedDB, Plugin Data, Service workers... EXCEPT COOKIES which behave correctly. This is due to WebExtension API limitations as stated here #1395 (comment)
Describe the solution that you'd like
Until the Firefox devs implement it properly, some safeguards can be tried to limit that frustrating global cleanup:
SOLUTION 1: when container support is enabled, pressing the
+ Whitelist
button should add the rule to ALL containers instead of just 1SOLUTION 2: this was proposed by @SpaceClicker here and it's probably a more elegant solution #1427 (comment) basically add a check that goes something like this:
if www.example.com localStorage whitelist rule exists in ANY container -> DO NOT cleanup
The idea is that if the user went out of his way to WHITELIST a website on 1 container, it's better user experience to be overcautious and let that data survive on all containers than it is to be too overzealous and delete that data on all containers.
The text was updated successfully, but these errors were encountered: