Cookiesafe should keep track of which cookies were added via a blocklist and remove them if the blocklist is removed
Bug #902764 reported by
Alexander Schlarb
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
CookieSafe |
In Progress
|
Wishlist
|
Alexander Schlarb |
Bug Description
Whenever you activate a blocklist in CookieSafe all the cookies of the blocklist are imported into the global cookie permission space and CookieSafe forgets about which Cookies permissions there are and just asks the browser each time it needs to know. Blocklists can have a lot of entries and removing every single entry which a blocklist provided can be very complicated and time-intensive so most users would probably just use the "Remove all"-button in the permissions dialog instead which isn't really a good solution.
Therefor CookieSafe should start keeping track of which Cookie permissions there are itself and just update the browsers internal CookiePermission list when necessary.
Changed in cookiesafe: | |
assignee: | nobody → Alexander Schlarb (alexander255) |
importance: | Undecided → Wishlist |
To post a comment you must log in.
Since I'm currently doing some fundamental changes to the cookie-permission module anyways, I might as well implement this idea now