Per site block rule doesn't prevent site's data in user's profile storage folder

Hi,

Forget Me Not 1.0.2 / Firefox 60.0.1 (x64) / Windows 7 (x64)

I’m encountering an issue with blocked sites that seems odd when compared to Firefox’s native site cookie block logic.

With Firefox / Options / Privacy & Security / Cookies and Site Data / Exceptions … If I set a site as blocked then are blocked not only the site’s cookies but as well LocalStorage and IndexedDB storage. By IndexedDB storage I mean a site’s data appearing in the user’s profile / Storage / Default folder, i.e https+++www.bostonglobe.com^firstPartyDomain=bostonglobe.com

Blocking with Firefox : no blocked site’s indexedDB storage Removing the site from Firefox blocking, adding the site to FMN as blocked : no cookies indeed but site’s data nevertheless in storage / default folder.

Here are my FMN defined rules:

As you can see among sites I’ve blocked appear those that keep data in the user’s storage folder: bostonglobe, huffingtonpost, techradar, theguardian

All these four domains will add data such as, i.e https+++www.bostonglobe.com^firstPartyDomain=bostonglobe.com This data is removed once Firefox closed, but remains during the session. If I add these domains to Firefox’s cookie blocking, their data is not added to user’s local/default folder.

Same applies to localStorage : a site set as blocked by FMN doesn’t prevent that site from installing data in user’s localStorage (webappstore.sqlite).

I hope you’ve understood what I mean as English is not my mother-tongue together with the fact I lack technical terminology.

[Lusito]

Hello and thanks for your feedback.

Sadly, there is currently no API available to block indexedDB, localStorage, etc. I can only block cookies at this time. If you look at the description of the black rule, you’ll see, that it’s only about cookies.

So this is an issue that mozilla needs to fix before I can do anything about it. I will do my best to convince them that this shortcoming should be fixed.

[Lusito]

@rugabunda Site-Bleacher can do that on chrome, as chrome seems to support it: https://developer.chrome.com/extensions/browsingData#specific_origins But on Firefox it will clear IndexedDB from ALL domains. Firefox doesn’t support cleaning IndexedDB per-domain.

Quote From Mozilla

This property only applies to cookies and local storage items. Only remove cookies and local storage items which are associated with these hostnames.

You added the wrong link about the indexedDB enumeration btw: https://bugzilla.mozilla.org/show_bug.cgi?id=934640

Enumerating the databases would allow to remove the databases, but only when the page is currently active. This is not a good solution, as the webpage could in the same moment recreate the databases.

A better solution would be to support hostnames in the browsingData.remove() function. There is a ticket for that here: https://bugzilla.mozilla.org/show_bug.cgi?id=1551301