Cookie clearing exceptions don't work after Arkenfox 102
See original GitHub issue🟥 https://github.com/arkenfox/user.js/wiki/5.2-Troubleshooting
- I have read the troubleshooting guide, done the checks and confirmed this is caused by arkenfox
- unchecked issues
maywill be closed as invalid
- unchecked issues
🟪 REQUIRED INFO
- Browser version & OS: Firefox 102 on NixOS Unstable
- Steps to Reproduce (STR):
- Go to GitHub
- Allow it to save cookies via the Ctrl+I menu
- Log in
- Restart Firefox
- Expected result: You are still logged in
- Actual result: You are no longer logged in
- Console errors and warnings: none
- Anything else you deem worth mentioning:
My overrides
// CONVINIENCE
// -----------------------------------------------
// Enable urlbar searching
user_pref("keyword.enabled", true);
user_pref("browser.search.suggest.enabled", true);
user_pref("browser.urlbar.suggest.searches", true);
// Enable session restore
user_pref("browser.startup.page", 3);
// Remember the file download location
user_pref("browser.download.useDownloadDir", true);
// Don't clear history
user_pref("privacy.clearOnShutdown.history", false);
user_pref("privacy.cpd.history", false);
// Enable DRM
user_pref("media.eme.enabled", true);
// REMOVE USELESS FEATURES
// -----------------------------------------------
// Disable search engine suggestions in the urlbar
user_pref("browser.urlbar.suggest.engines", false);
// Disable container tabs
user_pref("privacy.userContext.enabled", false);
user_pref("privacy.userContext.ui.enabled", false);
// Don't save passwords
user_pref("signon.rememberSignons", false);
This worked as intended until the last version, but since v102 it no longer works.
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:38 (16 by maintainers)
Top Results From Across the Web
How to set exceptions for automatic cookie-clearing on closure?
Exception only work if you let the cookies expire and won't work if you clear all cookies manually or via "Clear history when...
Read more >Cookies and Site Data exceptions not saving? : r/firefox - Reddit
"Delete cookies and site data when Firefox is closed" will only allow the cookies that have exceptions to remain after exit.
Read more >4.1 Extensions suggestions [CookieBro + Chameleon ... - GitHub
Cookiebro is by far the best cookie cleaning addon to date; ... back 4 months or more, even after explicitly using the "clear"...
Read more >Firefox 105 is out: here is what is new - gHacks Tech News
Firefox 91.x ESR will be upgraded to Firefox 102 ESR ... Security updates are revealed after the official release of the web browser....
Read more >Edge does not remember delete cookies on close exceptions
I'm trying to define "Do Not Delete" exceptions for cookies in the settings, but after you restart Edge, these settings will be deleted....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is #1507 - basically changes are
network.cookie.lifetimePolicy
=2
privacy.clearOnShutdown.cookies
+privacy.clearOnShutdown.offlineApps
= falseThe reason it didn’t occur until 102 for AF users, is that we used the lifetimePolicy pref instead of clearing all cookies + offlineApps data on close. 102 then had a migration to reset lifetimePolicy etc, effectively making it useless, and we had to change. They have now backed that out in FF/ESR102.01
There are two issues going on here. One is the sanitize onStartup fallback (when sanitize onShutdown fails) doesn’t respect exceptions, this is fixed in 103. This means when Firefox doesn’t exit gracefully, e.g. exiting the app with the OS shutdown, or crashing, then everything gets wiped.
The second issue is this is still happening for users who do (presumably) exit gracefully - i.e not crashing, and are exiting nicely with processes etc. Something is either failing to respect exceptions onShutdown, or it is triggering a sanitize on startup.
In 103, we HAVE to move to using onShutdown (and ignoring lifetimePolicy) because that migration code is there in 103+, and all we would be doing is triggering the migration code every time we start the browser. I DO NOT KNOW if the issue will persist in 103 - it depends on the cause: some permission thing, some race condition, something else, IDFK.
But for 102, and since this is also used for ESR users, I am putting out a dot release to revert the behavior.