Closed Bug 304953 Opened 19 years ago Closed 19 years ago

Firefox cache UI

Categories

(Firefox :: Settings UI, enhancement)

x86
All
enhancement
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 188720

People

(Reporter: mike, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050802 Debian/1.7.10-1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050802 Debian/1.7.10-1 Firefox lacks UI to allow the user to change the value of browser.cache.check_doc_frequency. For users coming from Netscape/Mozilla suite, changing the integer value found under about:config is substantially harder than the UI that was offered by Mozilla under Advanced/Cache, where it was immediately obvious when the browser would use cached content. A cache section under Tools/Options/Advanced that returned UI for the two preferences:- browser.cache.disk.parent_directory browser.cache.check_doc_frequency would be an appreciated enhancement. Users here who work on basic HTML pages get confused by the caching - this preference might help to alleviate that. Reproducible: Always Steps to Reproduce:
*** This bug has been marked as a duplicate of 188720 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Summary: Firefox cache UI → Firefox cache UI
Is the wontfix status on bug 188720 an indication that FF policy is not to expose these settings, or just an indication that there's no developer time available to do so? It's quite frustrating to see stuff assigned WONTFIX without any explanation of what exactly that means, or the reasoning behind it.
Bug 188720, comment #3: "The prefs have been reworked and this is not part of the plan. " WONTFIX means that the dev team have decided against a change - thinks with no time available are supposed to be left open, in case any one every wants to take the bug (at least that is the system as I understand it).
Status: RESOLVED → VERIFIED
"The prefs have been reworked and this is not part of the plan." That comment was two and a half years ago, and no rationale was given for it then. Is there nowhere for users to comment on this sort of thing, and no opportunity to have any input into this sort of decision. As someone responsible for deploying Mozilla products across an organisation, I am often frustrated by the seemingly arbitrary and opaque nature of the decision making processes.
(In reply to comment #4) > > That comment was two and a half years ago, and no rationale was given for it > then. Is there nowhere for users to comment on this sort of thing, and no > opportunity to have any input into this sort of decision. As someone > responsible for deploying Mozilla products across an organisation, I am often > frustrated by the seemingly arbitrary and opaque nature of the decision making > processes. I can only suggest one of the links from http://www.mozilla.org/developer/
You need to log in before you can comment on or make changes to this bug.