Closed Bug 255544 Opened 20 years ago Closed 11 years ago

UI for about:cache (a cache manager)

Categories

(Firefox :: General, enhancement)

x86
All
enhancement
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: snap.56k, Unassigned)

References

Details

(Keywords: conversion, Whiteboard: parity-ie)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.7) Gecko/20040803 Firefox/0.9.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.7) Gecko/20040803 Firefox/0.9.3

I think Firefox should have a better UI than about:cache to manage the cache.

What Cache Manager could have:
- order feature (by date, url, filesize, filename, filetype)
- delete button (to delete a file stored in the cache)
- blacklist (disable cache for too big/small files, filename, filetype, web
site, ...)

Reproducible: Always
Steps to Reproduce:




Well, I know some people who don't agree, they say I should make my own
extension. But I know people who agree and in doubt, I fill a new bug. Sorry if
it's a mistake :(
Confirming bug based on:

1. It's useful.
2. IE users are used to it.
3. about:cache is virtually undiscoverable.

Prog.
Blocks: 164421
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: conversion
Whiteboard: parity-ie
OS: Windows XP → All
'Delete' -> 'Doom' (because entries may not be deleted when active...)

*** Bug 264114 has been marked as a duplicate of this bug. ***
*** Bug 345165 has been marked as a duplicate of this bug. ***
A firefox extension "CacheViewer" implements a GUI with search and order capabilities, but doesnt include sort by filename/filetype, or the other more invasive parts of this RFI.

https://addons.mozilla.org/firefox/2489/
Assignee: bross2 → nobody
Version: unspecified → Trunk
I consider the addon is enough. WONTFIX this one?
This is a good area for an addon to implement, since it can provide a level of detail that is not needed for the majority of Firefox users.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.