Private browsing stuck. Help please?
I'm switching permanently from Chrome and this is the first problem I've run into. I had Firefox set to never remember history before, but since it's going to be my primary browser now I need it to remember cookies. Every time I try to change the history setting it pops up with "Firefox must restart" but when it restarts the setting is still set to never remember history and it just pops up again. How can I fix this? Already tried custom setting for history and browser.private.autostart and they didn't work either.
Ideally I'd like firefox to remember cookies but not history, but it's not a major issue if it has to have both.
Seçilen çözüm
Thank you for sharing your browser data. Next to your question, in
Question details > More system details
way at the bottom, it mentions you have a user.js file. That is an optional settings file that can be used to inject settings at startup which will override what you saved in your previous session. You need to check what is in that file or if you didn't create it yourself, remove it, to rule out that file as the culprit. More info here:
How to fix preferences that won't save
Bu yanıtı konu içinde okuyun 👍 0Tüm Yanıtlar (2)
Hi frostedhearth, Try this: Go to your History settings Select "Use custom settings for History" Select "Clear History When Firefox closes" Select "Settings" Make your selections in the Settings window.
(This may work in conjunction with the "Delete cookies and site data when Firefox is closed" option in the Cookies and Site Data section ???)
user104147805413306348376805769878442569366 tarafından tarihinde düzenlendi
Seçilen çözüm
Thank you for sharing your browser data. Next to your question, in
Question details > More system details
way at the bottom, it mentions you have a user.js file. That is an optional settings file that can be used to inject settings at startup which will override what you saved in your previous session. You need to check what is in that file or if you didn't create it yourself, remove it, to rule out that file as the culprit. More info here: