Cookie-autodelete: Always delete cookie from a domain, or never save cookie (Blacklist, possibly per container)

[zmulk]

Describe the Feature

I want to add a domain or website where the cookies never will be saved, or will be deleted directly.

[pwd-github]

That options exists with the "Clean After Tab Close" option.

[ke-d]

So a blacklist basically?

[MrGlasspoole]

You closed my Feature Request #210 as duplicate of this one.
This one talks about deleting cookies from sites on a blacklist.
I talk about rejecting all cookies by default (not first allowing and then deleting them).

Also at #156 i can read "134 resolved" but i don't see a blacklist?

[ke-d]

@MrGlasspoole

This one talks about deleting cookies from sites on a blacklist.
I talk about rejecting all cookies by default (not first allowing and then deleting them).

It is sort of related since if I ever implement a blacklist, it would be similar to a greylist where you can add a wildcard in the list to make that the default.

Also, the only thing I can do with current APIs is basically checking the onChanged event after a website has already set cookies and remove them after, which is not really a true "blacklist".

Another thing with #44 is that it requires at least 1 cookie to be set so that the browsingData API knows which domains to clear localstorage from. That part would not work if people start using a blacklist.

Anyways I'm open to suggestions on this.

Also at #156 i can read "134 resolved" but i don't see a blacklist?

That was a mistake. I selected the wrong issue but forgot to change it until you mentioned it.

[ElhemEnohpi]

@zmulk you can use the built-in blacklist feature of the browser. In Vivaldi go to vivaldi://settings/content/cookies and add a "block" exception for the site. This will prevent cookies and local storage from being used.

The Cookie AutoDelete description says "You must enable cookies in the browser as this extension will replace the internal cookie manager", but that's not really accurate. The internal cookie manager isn't replaced, it still works as usual. You can use it to block certain sites' cookies, or even to block all cookies by default and only allow certain ones, which will then be auto-deleted. (Or not, if you also whitelist them in C-AD).

[drcheap]

Also, the only thing I can do with current APIs is basically checking the onChanged event after a website has already set cookies and remove them after, which is not really a true "blacklist".

Given they would only last for a matter of milliseconds, or at least not long enough to ever be sent to a server in a future request, that would be equally as effective as a true blacklist.

[thomasrussellmurphy]

I would also be interested in seeing a feature to immediately delete cookies from select domains. Setting the blacklist to * (processed after whitelist/graylist) would be one option, but I'd welcome the option to only instantly remove cookies set by unwanted sites.

[grenzor]

Looks like functionality to do this landed in Nightly: https://bugzilla.mozilla.org/show_bug.cgi?id=1363860

Btw, is this a dupe of #95?

[ElhemEnohpi]

@grenzor , no, that doesn't help with this issue. And #95 is not the same issue as this one, though they both could maybe be fixed with the same solution, depending how it's implemented.

[kathampy]

I'd also like to blacklist a domain in the default container alone, but not in the separate container I use for that domain. This prevents me from using the browser settings to block cookies for the domain.

[Existencielle]

Hello,
my original request #450 ("Add "Blacklist" option beside Greylist and Whitelist") was closed, saying it was a duplicate of this one.

Here I do find the suggestion that I should just block cookies for that domain in Firefox settings.
I tried that, but it does not have the desired effect. Blocking cookies completely sometimes prevents pages from loading properly. What I want is the cookies to be accepted, but then after the grace period (I have set 6 seconds, don't remember if that is the default) them to be thrown away.

It may still be appropiate to merge my issue into this one, however I wanted to point out that the workaround suggested in this thread is not helping.

[pavinjosdev]

@zmulk Cookies can be blocked for specific sites by the browser's own cookie manager/settings. Docs for Chrome.

Blocking cookies completely sometimes prevents pages from loading properly.

@Existencielle Good point, I haven't found an open source extension to delete cookies every x seconds but as a workaround what I do is set the cookie to read only or protected status from an extension like EditThisCookie

[ElhemEnohpi]

Fyi, Forget Me Not supports blacklist rules, as well as a default "block" action for sites that don't have any rule set for them.

[ghost]

CookieMaster

allows you to control which sites are allowed to set cookies

[dhowe]

+1 for a true blacklist = don't allow cookie to be set (you can do this with the current API)

[Existencielle]

+1 for a true blacklist = don't allow cookie to be set (you can do this with the current API)

You do realize you don't need an addon for that, you can just set that in the Options?

I think the features that Cookie-AutoDelete provides should be stuff you cannot do without it.

[kathampy]

You do realize you don't need an addon for that, you can just set that in the Options?
I think the features that Cookie-AutoDelete provides should be stuff you cannot do without it.

You cannot block cookies per container. I want to block a certain domain's cookies in the Default container, but allow them in the domain's dedicated container.

[kennethtran93]

Apologies for temporarily closing this feature - I've adjusted the main issue to reflect the feature.

[thomasrussellmurphy]

Thank you for re-opening and cleaning this up. Looking forward to this potential enhancement.

[MPeti1]

So far Forget Me Not seemed to be the best for the task. Though from C-DA's name, I would have thought it can do proper blacklisting too.. (not cookie blocking, but deletion on tab close or whatever, so inverting the current functionality). At least now that I know that the dev doesn't want that, I won't check it every few months if they've added that feature

[kennethtran93]

This requires an overhaul of the UI elements within the popup as well as how it is displayed in the List of Expressions Table and will take some time.