Closed Bug 222847 Opened 21 years ago Closed 8 years ago

Don't enable clear cache button if only chome entries are cached

Categories

(Firefox :: Settings UI, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jmd, Unassigned)

References

Details

Enter Options->Privacy->Cache. Hit clear button. Notice it is disabled. OK Options dialog. Enter Options->Privacy->Cache. Notice clear button is again active. about:cache shows a few chrome: entries cached. I think this will cause users confusion, or to not really believe Mozilla is fully clearing it's cache. Normal users have no need to ever forcibly empty a cache consisting of a few chome entries, so keeping this behavior around as a feature seems to be of no benefit. The problem is especially glaring if you "clear all" of the privacy information, then reenter Options only to see cache "already" apperently has private data in it again.
*** Bug 240296 has been marked as a duplicate of this bug. ***
You may also have a look at bug 246910 that describes a similar, but sporadical problem. [Please change OS to "All"!]
I found out that if I restart Firefox after I have deleted the cache there are some more chrome:// items listed in about:cache _and_ a non-chrome:// item, the google-icon of the search bar! Maybe this causes the problem!?
no, that's different. There's been a lot of testing on this one, we know the issue.
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → preferences
Assignee: bross2 → nobody
We no longer disable the button at all, as far as I can tell, so this is effectively 'works for me' because the button is always enabled, even after clicking it -- but we also update the display of how much disk space is taken up by the cache, so that will read '0' and hopefully convince users that we are indeed serious about clearing the cache.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.