Is there any Firefox extension to automatically reject cookie popups?
Is there any Firefox extension to automatically reject cookie popups?
Hämta Cookie AutoDelete för Firefox. Control your cookies! This WebExtension is inspired by Self Destructing Cookies. When a tab closes, any cookies not being used are automatically deleted. Keep the ones you trust (forever/until restart) while deleting the rest. Containers Supported
addons.mozilla.org/en-US/…/consent-o-matic/
This add-on is built and maintained by workers at Aarhus University in Denmark. We are privacy researchers that got tired of seeing how companies violate the EU’s General Data Protection Regulation (GDPR). Because the organisations that enforce the GDPR do not have enough resources, we built this add-on to help them out.
Nice!
Not an answer, but a warning: I’ve tried a couple of them and they may break some sites and I found very difficult to debug (probably because how many addons I have). If you notice weird things, try disabling the addon.
I’ll try the recommmended Consent-O-Matic.
Avast bought it.
Thanks sir the note.
I use in Vivaldi blocker this filterlists, which can be added also in uBO, they are working fine.
addons.mozilla.org/en-US/firefox/addon/popupoff/
Popupoff simply removes those pop ups and since you can’t see the dialog to accept the cookies it is like not having given consent to cookies. (It sometimes makes the site not work properly, but you can set global and site specific to mitigate the issues.)
I even asked the developer here to make sure.
I also managed to install it on my android, to do this follow this guide blog.mozilla.org/…/expanded-extension-support-in-…
uBlock Origin to block 3rd party JS.
NoScript to specifically allow certain functions of certain domains serving JS.
Both of these combined make sure I never see such banners because, well, no JS allowed for most things.
Also Cookie Autodelete with Firefox containers. Even if someone happened to store cookies in my browser, they are gone by the time I close the tab. Also FF containers prevent the proliferation of cookies across tabs if in different profiles.
NoScript blocks (almost) everything by default. You can then allow, temporarily allow, or selectively allow specific types of capabilities that JS from a domain can run, on either every page or on the specific FQDN. Or you can explicitly block the script(s).
The reason I said almost in the first line is because you can customise the default behaviour of NoScript to allow/disallow certain capabilities to scripts you haven’t provided custom permissions/encountered before.