Closed
Bug 394028
Opened 18 years ago
Closed 18 years ago
The checkbox "cookies" in the dialog to delete private data does not remember status when it once has been checked
Categories
(Firefox :: General, enhancement)
Tracking
()
RESOLVED
INVALID
People
(Reporter: blubbman, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6
It is very annoying always having to check this checkbox again everytime i want to delete my personal data. It would be better if it remembered the status it had the last time one deleted personal data. I think in previous versions of Firefox this problem did not exist.
Reproducible: Always
Steps to Reproduce:
1. Open the Dialog to delete personal Data (Dont know the accurate name in English versions)
2. Check the Checkbox next to "Cookies" and close the dialog
3. Open the dialog again
Actual Results:
When you open the dialog again that box is not checked anymore
Expected Results:
The checkbox should be checked, because it has been checked before and it is very likely that i want to delete my cookies again (because i wanted so before).
This is also true for someone who does not want to delete cookies (If he did not want so last time he seems to prefer to keep his cookies).
I expected Firefox to remeber the status of the checkbox.
Comment 1•18 years ago
|
||
this could cause a dataloss if a user had previously choosen to delete cookies, and the next time he forgets to uncheck that...
you should be able to set the default options from Tools / Options / Privacy / Private data / Settings, so please try that
Comment 2•18 years ago
|
||
The dialog does not remember the settings from the last time that it was used, it takes them from the defaults in Tools->Options->Privacy->Private data->Settings
Reopen the bug if you still see a problem.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•