Deleting History, Cookies causes all entries in the exception cookie list to be deleted too.




8 years ago
5 years ago


(Reporter: Tamer Higazi, Unassigned)


(4 keywords)

Firefox Tracking Flags

(Not tracked)


(Whiteboard: [CLOSEME 2011-1-30])



8 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2) Gecko/20100129 Gentoo Firefox/3.6
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2) Gecko/20100129 Gentoo Firefox/3.6

I configured firefox that far, that after I close the browser the cookie exception (domains of URLS which need to place cookies) are entirely deleted too, what shouldn't be done. 

You have the possibility to delete all history with the combination: Strg-UpButton-Delete and there the exceptions list you set once before at Settings->Privacy->Cookie List are gone.

Reproducible: Always

Steps to Reproduce:
1. add domains in exception list
2. delete history throgh STRG-UP-DEL Key
3. all exceptions are gone too
Actual Results:  
the exception list is gone

Expected Results:  
that only history and stored cookies are gone, but not the exception domain list


8 years ago
Keywords: 64bit, dataloss, helpwanted, privacy

Comment 1

8 years ago
Yeah, I've noticed this, too, when manually using "Clear recent history ..." without the "cookies" check box.  One of the other choices also deletes the exception list.  If that's the design intent, I'd consider it a misfeature.  It's really annoying to have to add all the sites whose cookies I want to treat differently again.
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing.

You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version,
Whiteboard: [CLOSEME 2011-1-30]
No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile ( If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE

Comment 4

6 years ago
Still an issue in 3.6.23

Comment 5

5 years ago
Seems to work now in 13.0.1
You need to log in before you can comment on or make changes to this bug.