-
Notifications
You must be signed in to change notification settings - Fork 509
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: v97, v98, v99, v100, v101 #1370
Labels
Comments
ALL HAIL PANTSCollect the set |
to the person who stole my pokemon pijama last night: please return it asap. |
Closed
Closed
Closed
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🟩 v101
FF101 release notes
FF101 for developers
FF101 security advisories
nothing of consequence... I promise a new clean issue for v102
// user_pref("privacy.query_stripping.enabled", true); // [FF101+] [ETP FF102+]
0650
for prefsCleaner - RUN PREFSCLEANER )noopener
andwindow.name
have been default true since FF79 and FF86 respectivelytrimURLs
is cosmetic fluff, see remove 0803: browser.urlbar.trimURLs ? #1473cookie.thirdparty
is slated for removal upstream and may cause issues with the lifetime cookie pref deprecation and site exceptions, and is also covered by sanitizing on close🟩 v100
FF100 release notes
FF100 for developers
FF100 security advisories
9999: DEPRECATED / REMOVED
in user.js v100network.http.http2*
prefs🟩 v99
FF99 release notes
FF99 for developers
FF99 security advisories
v99 was cosmetic changes and one pref deprecated
9999: DEPRECATED / REMOVED
in user.js v99🟩 v98
FF98 release notes
FF98 for developers
FF98 security advisories
v98 was just cosmetic changes
🟩 v97
FF97 release notes
FF97 for developers
FF97 security advisories
OTHER NEWS
CHANGELOG: [all changes]
1 see #1299 - starting with v97, all changes to the live master happen once per release: all changes are done in a separate branch/PR and only merged when finished
⭐ your friendly reminder to ALWAYS run prefsCleaner
CHANGES
browser.safebrowsing.downloads.remote.enabled
is already false// user_pref("browser.safebrowsing.downloads.remote.url", ""); // Defense-in-depth
STATS
The text was updated successfully, but these errors were encountered: