(In reply to Simon Mainey from comment #10)
We want to keep both the allow and block options, which means you can still enable sanitize-on-shutdown and exempt sites from being cleared
Indeed, but users won't be able to add exceptions via permissions tab if you only have two options "Allow" and "Block". Which only leaves the slow human error-prone typing into "Manage Exceptions" including missing schemes and www etc - if that's how it has to be, so be it - and that was what my question was about
There are actually 4 states in the page info window (Permissions tab) for the cookie permission.
- "Use Default" checked
- Allow for Session
When we remove (3) "Allow for Session", you can still check "Use default", which effectively clears the permission. Selecting "Allow" will add an exception for that site. Does that answer your question?
(In reply to Asif Youssuff from comment #11)
I'm also confused about what the UI will look like/how this will work. For context, I wrote a post about my particular setup (with screenshots): https://www.quippd.com/writing/2021/07/26/firefox-privacy-stop-hardening-love-strict-etp.html#delete-cookies-when-closing-firefox
Basically, I set Firefox to Delete cookies and site data when Firefox is closed, then I override that preference on a site by site basis by using the Page Info panel.
Is this something that will continue to be supported? I guess in the parlance of this bug, I don't want to sanitize the cookies of the sites that I specify.
Yes, that will still be supported. Since you're checking "Delete cookies and site data when Firefox is closed" Firefox will clear all data on shutdown, skipping any sites you added as exceptions - exceptions being sites where you set cookies to "Allow".