Closed Bug 1030975 Opened 10 years ago Closed 8 years ago

Remove browser.cache.use_new_backend_temp once automation is no longer using it

Categories

(Core :: Networking: Cache, defect)

32 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 913828
mozilla33
Tracking Status
firefox30 --- unaffected
firefox31 --- unaffected
firefox32 - affected
firefox33 --- affected

People

(Reporter: mayhemer, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-backlog])

and set browser.cache.use_new_backend to 1 by default or even rename this pref to something more sane.
Thanks for filing :)
OS: Windows 7 → All
Hardware: x86_64 → All
Target Milestone: --- → mozilla32
Version: 31 Branch → 32 Branch
Target Milestone: mozilla32 → mozilla33
Blocks: cache2polish
I don't think this needs to block beta in any way.  This is just a pref cleanup.
(In reply to Jason Duell (:jduell) from comment #2)
> I don't think this needs to block beta in any way.  This is just a pref
> cleanup.

Tracking- based on Jason's comment.
Depends on: 1053517
Summary: Remove browser.cache.use_new_backend_temp → Remove browser.cache.use_new_backend_temp once automation is no longer using it
I'm wondering when these preferences are going to be removed.
The new cache is enabled by default since version 32 of the Firefox browser, but the preference still exists ( browser.cache.use_new_backend;0 AND browser.cache.use_new_backend_temp;true )

It may cause confusion to some users, since they'll think the new cache is disabled while verifying that the browser.cache.use_new_backend value is 0.
Really? Fast forward to Nightly 46 and the prefs are still there...
You guys really need to do some cleanup now...
Whiteboard: [necko-backlog]
I would like to take this bug. Please tell me what "browser.cache.use_new_backend" should be renamed to.
Flags: needinfo?(honzab.moz)
I intend to remove this with the old cache code.  No need to change this in the meantime.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(honzab.moz)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.