Options->Cookies->Exceptions: frustrating

Help

I feel like the exceptions box is designed to frustrate users.

  1. http:// and https:// require separate entries

  2. typing a domain into the box and then hitting enter defaults to "allow"

  3. there is no way to change the status of an entry from "block" to "allow", you have to retype it

  4. doesn't accept wildcards, so that if you want to un-Google you have to block google.com, google.ca (and then include separate entries for http/https!) Why not just *.google.* ?!

  5. "keep until" box doesn't have a "until I have no browser tabs open to that domain"

Why? Why make this stuff frustrating? Why make giving access to my cookies to a 3rd party part of basic privacy?

Posted Mar 18, 2018, 3:57 PM UTC

264
EstherMoellman•

Other additional frustrations:

  1. Users can't add different domains separate by "," or ";" etc. They need to enter one by one.

  2. It is impossible to import or export saved exceptions.

  3. If users need to refresh Firefox or to install a new one... bye bye saved exceptions.

  4. Users need to remember to save entered exceptions. The simple addition of a domain don't save the exception.

  5. If users are browsing, and a domain breaks due to blocked cookies, there is no notification from FF alerting that. Users need to guess the problem, open the "options" page, add the exception etc etc etc... a long bizarre process.

7
anonymousjonOP•

How about right click -> "Protect" which deletes cookies from that domain (and clears associated cache) and then adds the domain and all referrals to blocked list.

That'd be pretty helpful!

3
Luke-BakerNightly Windows 10•

Site permissions, including cookie exceptions, are stored in permissions.sqlite in the profile folder.

1
[deleted]•

There once was an addon which made this stuff way more easier, but everything changed when the fire nation WebExtensions attacked.

1
Wagner_HollowKRD•

From my point of view, the worst was when Firefox-v57 (aka Firefox Quantum) was published. Because Mozilla didn't provide the API about the Cookies (Exceptions list). That's why today (april 2018 and even Firefox-v61) I won't migrate. Because I didn't find any addon (neither with Cookie AutoDelete, Cookiebro , etc) in the aim to replace Cookie Keeper.


lockPref("network.cookie.lifetimePolicy",2); lockPref("network.cookie.cookieBehavior",2);


To resume, right now there is nothing as WebExtensions which can correct this trouble.

1