dessant / clear-browsing-data

Browser extension for clearing browsing data, available for Chrome, Edge and Firefox
https://addons.mozilla.org/en-US/firefox/addon/clear-browsing-data/
GNU General Public License v3.0
185 stars 22 forks source link

Local storage isn't being cleared #20

Closed siffegh closed 5 years ago

siffegh commented 5 years ago

System

Bug description Local storage isn't being cleared by the extension. Looking at FF Options > Privacy & Security > Cookies and Site Data > Manage Data, storage is not cleared until doing it inside the FF option:

Screenshot_1 Screenshot_2 Screenshot_3

Logs Screenshot_4 Screenshot_5

dessant commented 5 years ago

Are you sure that it is the local storage and not the cache? The storage column in the Firefox preferences also includes other data types. There is a known Firefox bug that prevents extensions from clearing data stored with the Cache API: https://bugzilla.mozilla.org/show_bug.cgi?id=1526246

Local storage is cleared on my part, you can test it with this demo: http://jsfiddle.net/ccatto/G2SyC/2/

siffegh commented 5 years ago

Not sure how to run/view that demo. Cache is being cleared (C:\Users\Administrator\AppData\Local\Mozilla\Firefox\Profiles\8k367gi5.NewTest).

After clearing LS: Screenshot_1

Files also remain in C:\Users\Administrator\AppData\Roaming\Mozilla\Firefox\Profiles\8k367gi5.NewTest\storage\default: Screenshot_2

Screenshot_3

siffegh commented 5 years ago

Cache folder - meant C:\Users\Administrator\AppData\Local\Mozilla\Firefox\Profiles\8k367gi5.NewTest\cache2.

dessant commented 5 years ago

It's hard to reproduce the issue without having step by step instructions, I have tried, but the data is cleared on my part. Please share step by step instructions with a jsfiddle that stores data only in local storage, and make sure to refresh the options page or devtools before checking if the data was deleted.

dessant commented 5 years ago

If you do manage to reproduce the issue in a controlled way, please also open an issue for Firefox, because if valid, this can only be a browser bug.