Closed Bug 142970 Opened 23 years ago Closed 23 years ago

Clear Cache should be disabled after clearing

Categories

(Core :: Networking: Cache, defect)

defect
Not set
minor

Tracking

()

VERIFIED DUPLICATE of bug 66012

People

(Reporter: bamm, Assigned: bugs)

Details

The Clear Cache and Clear Memory Cache buttons in the prefs dialog should be disabled when the cache is empty. In particular, they should be disabled immediately after clearing and enabled only when new files have been added to the cache folder. The current behavior is confusing as it gives users the impression that nothing has happened, and an urge to clear it again seeing that it is still clickable. Disabling it is a good visual confirmation that the action they requested has actually been completed.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Maybe this is a dup of bug 66012, or it depends on that one.
I think it's the other way around.
Blocks: 66012
Resolving as duplicate. If this is not a duplicate, reopen. *** This bug has been marked as a duplicate of 66012 ***
No longer blocks: 66012
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Andrew: The other bug wants a confirmation, possibly a dialog. However, /even if/ a confirmation dialog is given (which will fix the other bug), the Clear Cache button still needs to be disabled - there is no point in it being enabled if there is nothing to clear.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
it's the same bug. the fact that one suggestion in it is for some prompt doesn't override the fact that the bug's main request is precisely what you are requesting. *** This bug has been marked as a duplicate of 66012 ***
Status: REOPENED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → DUPLICATE
marking verified as a duplicate. if you decide to reopen this bug, please clarify why. search string for bugspam removal: SalviaGuaranitica
Status: RESOLVED → VERIFIED
Component: Preferences → Networking: Cache
You need to log in before you can comment on or make changes to this bug.