yokoffing/Betterfox 110.0

user.js v.110

on GitHub

🦊 Firefox Release

• FF110 release notes
• FF110 for developers
• FF110 security advisories

✅ Betterfox Updates

• Changelog

🗒️ Release Notes

• 👁️ Users can now right-click -> Reveal Password in password fields to see their passwords. This is helpful if a website doesn't provide the little eye icon.
• 🔒 Removed HTTPS-Only Mode in favor of HTTPS-First Policy. Firefox will always attempt HTTPS connections, but it will fall back to HTTP if a secure connection isn't available. While Mozilla enabled this policy in v.91 for private windows, Betterfox will now enforce it for normal windows, too.
  • In doing so, this:
    • Lowers the chance of unintended site breakage, and falls in line with Betterfox's goal of everyday use cases like school and work.
    • Matches parity with Brave and Edge.
    • Still allows users to easily toggle HTTPS-Only Mode as needed.
  • We also enabled the URL bar to display "Not Secure" text on HTTP sites.
  • Note that HTTPS Only Mode prefs were removed but not reset, since there are big proponents of this feature.
    • Unless you’re applying this user.js to a new profile, you must manually disable it if you want these more relaxed settings.
• ⛔ Reset dom.popup_allowed_events as it caused unintended breakage. The pref did not improve protection in real world usage when compared to Firefox's default settings and pop-up blocking filters in ad blockers.
  • e.g., Out of 50 times a new window was blocked, only 1 of those times did we want this action.
• ⏩ Removed dnsCacheExpiration prefs as these are easily overridden by the DNS resolver, especially if using DoH/DoT.
• 🕵️‍♂️ Removed RFP prefs due to known issues. These prefs have low utility for Betterfox's context. See https://github.com/arkenfox/user.js/issues/1618.

Keyword Summary

• removed = the change applies to new profiles; you must manually reset the pref in existing profiles
• reset = the change applies to both existing and new profiles