clearObsoletePrefs is useless

VERIFIED FIXED in Firefox 2 alpha1

Status

()

P3
normal
VERIFIED FIXED
13 years ago
12 years ago

People

(Reporter: Gavin, Assigned: Gavin)

Tracking

({verified1.8.1})

Trunk
Firefox 2 alpha1
verified1.8.1
Points:
---
Bug Flags:
blocking-firefox2 -

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

It tries to clear saved user prefs that have long been removed from the default
pref file, and it does this every time a new window is launched. It should just
be removed, since it's no longer useful.
Target Milestone: --- → Firefox1.6-
Status: NEW → ASSIGNED
Created attachment 199760 [details] [diff] [review]
patch

timebomb.first_launch_time:
not used, gone since forever

network.cookie.enable:
not used

network.cookie.denyRemovedCookies:
not used in firefox.js

network.cookie.enableForOriginatingWebsiteOnly:
not used

enableForCurrentSessionOnly:
not used, needs to be removed from firefox.js as well

network.cookie.warnAboutCookies:
still appears to be used, but no default

browser.search.defaultengine:
Referred to by OpenSearch() in browser.js but nonexistent. (bug 203959 is for
cleaning that method)

print.use_global_printsettings, print.save_print_settings:
Reintroduced in bug 118563, so clearing them is a bug...
Attachment #199760 - Flags: review?(bugs.mano)
Priority: -- → P3
mozilla/browser/base/content/browser.js; new revision: 1.523;
Status: ASSIGNED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → FIXED
Attachment #199760 - Flags: approval1.8.1?

Updated

13 years ago
Flags: blocking-firefox2? → blocking-firefox2-

Updated

13 years ago
Attachment #199760 - Flags: approval1.8.1? → branch-1.8.1?(mconnor)

Updated

13 years ago
Attachment #199760 - Flags: branch-1.8.1?(mconnor) → branch-1.8.1+
Checked in on the branch.
mozilla/browser/base/content/browser.js; new revision: 1.479.2.55;
Keywords: fixed1.8.1
Target Milestone: Firefox 2 → Firefox 2 alpha1
VERIFIED by code inspection.
Status: RESOLVED → VERIFIED
Keywords: fixed1.8.1 → verified1.8.1
You need to log in before you can comment on or make changes to this bug.