New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
changelog: v105 #1559
Comments
Thank you ❤️ |
good milestone of getting down to 130 pref flips: a year ago (v91) we were 167 and the release prior to that (v90) was 188. What a difference a year makes!
|
just added some counts. holy guacamole ... v51, our first release on github. 391 active prefs (not flips, IDK what was enforcing defaults), although TBH, I think there was a lot of fluff in that (e.g. redundant/fallback safe browsing, etc) and some deprecated prefs, and probably some semi-dodgy choices, and we were fairly hard-core with opsec etc here's the cleanout (or shitshow?) in v67 - #732 So by FF68 in July 2019 we were 255 [edit: active] prefs listed, and just over three years later, today on v105 we are 155 [edit: active] prefs listed. At this rate I can retire in 2027 and stay drunk |
won't be long until CRLite is also the default: https://bugzilla.mozilla.org/show_bug.cgi?id=1795710#c18 |
date: 5-October-2022
FF105 release notes
FF105 for developers
FF105 security advisories
CHANGELOG
browser.newtab.preload
+ cleanup AS #1556⭐ your friendly reminder to run prefsCleaner
The text was updated successfully, but these errors were encountered: