[meta] Clean up old preferences
Categories
(Core :: General, task)
Tracking
()
People
(Reporter: tjr, Unassigned)
References
(Depends on 87 open bugs)
Details
(Keywords: meta)
User Story
For the purposes of this metabug, a preference is considered old if it has existed for at least one year.
We have a lot of old preferences that add to process startup and runtime, test and code complexity and don't provide much value for even advanced users. This bug will track identifying them.
I'm going to flag some bugs under it that are rolling out Nightly-only features to release, it would be great to have tooling to remind us to go back and remove those prefs too.
Reporter | ||
Updated•2 years ago
|
Reporter | ||
Comment 1•2 years ago
|
||
I'm doing an initial search through of prefs with 'enabled' or 'disabled' in the name that are 3+ years old and don't appear from a cursory search to be flipped in any unusual configuration or would need to be flipped by end-users. It's entirely likely I'm wrong about many of these, so please just WONTFIX them as appropriate.
Comment 2•2 years ago
|
||
Bug 1734056 and the bug duped to it have a bunch of old plugin related pref stuff.
Updated•2 years ago
|
Updated•1 years ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment hidden (duplicate) |
Comment 5•1 year ago
•
|
||
maybe
privacy.partition.serviceWorkers
- been default true since FF105privacy.partition.always_partition_third_party_non_cookie_storage
- default true since FF109privacy.partition.always_partition_third_party_non_cookie_storage.exempt_sessionstorage
- default false since FF109
edit: what happened there, it un-depended those 4 bugs?
Comment 6•1 year ago
|
||
Please open new bugs instead of commenting on the meta.
Description
•