Closed
Bug 47056
Opened 25 years ago
Closed 23 years ago
memcache debug option is broken
Categories
(Core :: Networking: Cache, defect, P3)
Tracking
()
RESOLVED
FIXED
Future
People
(Reporter: dougt, Assigned: gordon)
References
Details
(Keywords: helpwanted, Whiteboard: [nsbeta3-][cache])
The debug preferences panel for mem cache is broken.
The pref string in /xpfe/components/prefwindow/resources/content/pref-debug.xul
is specified as browser.enable.cache,
<checkbox id="browserEnableCache" value="&debugEnableMemCache.label;"
110 pref="true" preftype="bool" prefstring="browser.enable.cache"
111 prefattribute="checked"/> whereas the actual pref string
defined in all.js for mem cache is browser.cache.enable
pref("browser.cache.enable", true);
Since this is set to true, mem cache is enabled.
Neeti didn't we add this to an existing bug on mem cache already? I think I
did... but I can't remember that bug.
ok then... marking as dup.
*** This bug has been marked as a duplicate of 30670 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
This is not a duplicate of 30670
Status: VERIFIED → REOPENED
Resolution: DUPLICATE → ---
Nominating for nsbeta3, since 30670 was nsbeta3+
Status: REOPENED → ASSIGNED
Keywords: nsbeta3
Comment 9•24 years ago
|
||
This is simple. Someone could help us with this.
Keywords: helpwanted
Whiteboard: [nsbeta3+]
Comment 10•24 years ago
|
||
Debug panel is not in release builds.
Work around is change the pref in the pref file.
Whiteboard: [nsbeta3+] → [nsbeta3-]
Target Milestone: --- → Future
Comment 11•24 years ago
|
||
Why do we blow off stuff like this, sure its not major or critical to release
since debug isn't in the commercial builds, but come on, its a pref check box,
how hard can simply fixing the correct status of a pref be? This I swear is
symptomatic of one of the few things that p@sses me off about this project,
lots of piddly little bugs that could be wiped off the charts with ease
(usually UI polish stuff for the mostpart), but get pushed back, marked future,
and never dealt with. Give poor Bugzilla a break and wipe out these trivial
bugs.
I noticed it myself when looking through the pref's of a completely fresh clean
install. Wish I had code knowledge, then I would go change it myself and submit
a patch. Anyways, on a side gripe, if no one has looked recently, the scroll-
bar not appearing in the pref's category scroll-box sometimes when the tree is
expanded needs to be fixed prior to 1.0, and the layout of a lot of the prefs
panels themselves in a default profile need to be fixed as well as they do not
fully appear on the default window dimensions. </endrant>
Assignee | ||
Comment 12•24 years ago
|
||
Currently the memory cache does not respect the enable pref because it is getting
initialized and used by ImgLib before we have any preferences. We haven't fix
this particular bug yet because we've been concentrating on crashers and bugs
that would appear in optimized builds (not just debug builds). Setting the
memory cache size to zero will have nearly (but not quite identical) effects as
disabling it. I may be able to fix this in 0.9.1.
Assignee: neeti → gordon
Status: ASSIGNED → NEW
Component: Preferences → Networking: Cache
Assignee | ||
Comment 13•23 years ago
|
||
This has been fixed.
Status: NEW → RESOLVED
Closed: 25 years ago → 23 years ago
Resolution: --- → FIXED
Updated•23 years ago
|
QA Contact: sairuh → benc
You need to log in
before you can comment on or make changes to this bug.
Description
•