Closed
Bug 276656
Opened 20 years ago
Closed 20 years ago
Disk cache size conversion (MB to KiB) is borked
Categories
(SeaMonkey :: Preferences, defect)
SeaMonkey
Preferences
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 106618
People
(Reporter: schapel, Assigned: schapel)
Details
Attachments
(1 file)
776 bytes,
patch
|
darin.moz
:
review-
|
Details | Diff | Splinter Review |
Reproducability: Always
Steps to Reproduce:
1. In Preferences, set Disk Cache to 1 MB.
2. Go to about:config and type "cache" for the filter.
3. Go to about:cache
Actual Results:
In step 2, browser.cache.disk.capacity is shown as 1024. In step 3, Maximum
storage size is shown as 1024 KiB.
Expected Results:
In step 2, browser.cache.disk.capacity is shown as 1000. In step 3, Maximum
storage size is shown as 1000 KB.
An alternative (and probably easier and safer) way to solve this is to change
"MB" to "MiB" in the cache preference dialog. That way, setting the disk cache
to 1 MiB would display as 1024 KiB in about:cache.
Assignee | ||
Comment 1•20 years ago
|
||
Assignee | ||
Updated•20 years ago
|
Comment 2•20 years ago
|
||
Comment on attachment 170781 [details] [diff] [review]
Patch to display MiB instead of MB in pref panel
No, I believe the decision was made to suppress MiB and KiB and instead use the
more familiar MB and KB in the user interface for mozilla products.
(about:cache is a special exception since it is a "geek feature" not intended
for use by normal users. Afterall, there is no way to access about:cache from
the UI.)
If anything at all is to be done about this bug (and I don't see there being
much urgency here), I think you could maybe argue that the UI should treat the
input in megabytes instead of mebibytes, but that would be inconsistent with
page-info and other parts of the product.
In short, I think it might be better for users if we kept with the more
familiar interpretation of MB and KB.
Attachment #170781 -
Flags: review?(darin) → review-
Comment 3•20 years ago
|
||
*** This bug has been marked as a duplicate of 106618 ***
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•