345165 - Improve useability of about:cache output

Status: RESOLVED DUPLICATE of bug 255544

(Firefox :: Bookmarks & History, enhancement)

Description

[Ruediger Bente]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4

The cache display, created by about:cache is not designed to find files or information in the memory and/or disk cache very easy. But from time to time it may helpful to get the information about files stored in the cache on a more user-friendly way, for example in a table form with the possibility to sort the different columns like key, fetch count, modification date or filename.
This may very helpful in the case of extracting files from the cache.
Another example is to delete single files (for example large ones) from the cache to keep the rest of the cache as it is and free up the storage. 

Reproducible: Always

Steps to Reproduce:
1.about:cache
2.
3.

Actual Results:  
The files in the cache.

Expected Results:  
The files in the cache are shown in a not very user-friendly way.

There is a extension available under
http://park2.wakwak.com/~benki/cacheviewer.html 
which creates a useful list in an external window.

Comment 1

[Anders Conbere]

The arguements I've heard against improving  ui for these sorts of places is that for they are really not meant to be used by the general public, and as such as long as they are sufficient for developers they're doing okay.  The reasoning given to not improve them simply because everything should be as nice and polished as possible were the following.

1) for each word you put in the about:cache dialog that's one more word that needs to be properly localized.  The localization teams are already under enormous strees to keep up with developement of front facing ui.

2) That's one more thing for a dev to do that could be spent working on something more important.

Basicaly, those dialogs only exist for a very narrow and specific function, and we don't have the man hours to spend fixing them and maintaining them.  As extensions do exist that improve the functionality that is probably the best place to look.

Comment 2

[Uriah Narmed]

Probably a dupe of bug 255544.

Comment 3

[Anders Conbere]

agreed

*** This bug has been marked as a duplicate of 255544 ***