Closed Bug 178944 Opened 22 years ago Closed 20 years ago

Add GUI preference to disable disk cache

Categories

(Camino Graveyard :: Product Site, enhancement)

PowerPC
macOS
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Camino1.0

People

(Reporter: Saarinen, Assigned: mikepinkerton)

Details

Attachments

(2 files, 1 obsolete file)

Navigator's disk cache size can get way out of hand if you aren't paying attention. There should be some preference you can set to limit the size of the cache. I have seen (in other browsers) days used (delete anything older than 7 days) as well as size (limit cache size to 20 megs). Either of these would be good options, though I think I prefer a size limit.
Sure.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
I would also like to see this feature. Many people have high speed connections and don't really need a cache. For me having a cache is a hindrance because it just frags my hard drive.
bump :)
Navigator does offer this, but not via GUI. Set a value (in KB) for 'browser.cache.disk.capacity' in your user.js file. For example, to set a 1-MB cache size: user_pref("browser.cache.disk.capacity", 1024); See also <http://preferential.mozdev.org/preferences.html> for further browser.cache settings.
Just me hacking some code and not yet being able to build. Wondering if it would be any good what Ijust did.
Adding the modified nib file, I should have a better look on how to make it better.
Updating summary to reflect comment 4, and adding to the 0.9 list so this can be included in the pref rewrite.
Summary: Preference for limiting disk cache size → Add GUI for preference to limit disk cache size
Target Milestone: --- → Camino0.9
Fixed a type O.
Attachment #147120 - Attachment is obsolete: true
We should make sure users can only give MB values instead of Kb's. That would be better t understand I guess. We should also only allow + values.
General comments: -Yes, we should do it in MB, not KB. This means that we might want to allow non-integer values (e.g., 2.5MB) and round to the nearest KB--probably not a big deal either way though, since resolution of less than 1MB is hardly necesary. -Since one very common request for this comes from users who want *no* cache, we should consider having a checkbox to disable/enable the cache, since that's more intuitive for the user than entering 0 MB. -What is the default value for this? Is it unbounded by default? What *should* our default be? Patch comments: browser.cache.memory.capacity isn't the right pref; that controlls the *memory* cache, which users shouldn't need to mess with.
Based on discussions, changing bug to "Add GUI preference to disable disk cache" (was "Add GUI for preference to limit disk cache size"). There is already a default limit on the cache size, and it's doubtful that most people would know what a good value would be (and not be able to edit user.js). Turning off the disk cache has relatively easy-to-understand/explain performance differences, and is rapidly becoming more useful as broadband becomes more common. Unless someone has a compelling argument for a GUI to change the actual cache size, we shouldn't add it. One thing we should test is the effect of disabling cache on favicons. I assume they would all be lost at every quit, which we would want to mention.
Summary: Add GUI for preference to limit disk cache size → Add GUI preference to disable disk cache
Recent discussions on irc.mozilla.org have leaned towards not adding this pref. Bumping this bug to 1.0 and taking it.
Assignee: sfraser → joshmoz
Status: ASSIGNED → NEW
Target Milestone: Camino0.9 → Camino1.0
Following further discussion there's general agreement that we don't want to expose this option in the GUI. As this is sometimes requested (though can't work out why myself - would have thought browsing with cache and then doing a browser reset was better) agreed to reassign to the help component and Jasper, so that it gets mentioned in the hints & tips somewhere. (Probably after about:config has been fixed.)
Assignee: joshmoz → camino
Component: Preferences → Help
Reassigning back to Mike, I think we should indeed not implement this. Instead we should add it to the hidden prefs page.
Assignee: camino → pinkerton
jasper, if you're writing that page, shouldn't you own this bug?
The "Hidden Preferences" page on caminobrowser.org documents how to disable this option. Following the discussion in comments 12-15 I believe we can resolve this as FIXED.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Mass move of mis-filed bugs out of obsolete component; apologies for bugspam.
Component: Help → Product Site
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: