Firefox

Firefox Beta and Developer Edition
Release Notes

Release Notes tell you what’s new in Firefox. As always, we welcome your feedback. You can also file a bug in Bugzilla or see the system requirements of this release.

149.0beta Firefox Beta

February 25, 2026

Version 149.0beta, first offered to Beta channel users on February 25, 2026

Firefox Beta gets updated 3 times a week and as a consequence, the release notes for the Beta channel are updated continuously to reflect features that have reached sufficient maturity to benefit from community feedback and bug reports.

Warning: Features listed here may or may not make a final release of Firefox.

In addition to these release notes, you can follow ongoing development via the Firefox Trains website or our @FirefoxBeta Bluesky account.

New

  • The WebRender layer compositor is now enabled on Windows, reducing power usage during full-screen video playback and improving WebGL/WebGPU performance.

  • Many PDF files will now load significantly faster thanks to hardware acceleration.

  • Address Autofill is enabled for users in Australia, India, Italy, Poland, and Austria

  • Firefox now automatically blocks notifications and permanently revokes permissions for any website flagged as malicious by SafeBrowsing. This prevents unsafe sites from sending background notifications to users, commonly used for ads, spam or phishing.

  • You can now add a Share button to your toolbar from Customize Toolbar. It lets you easily share the addresss of your current tab using your Windows or macOS Operating system’s sharing services.

  • Local network access restrictions are now being extended to all users. Firefox will require websites to request your permission before connecting to devices on your local network or to apps and services on your device. Previously limited to users with Enhanced Tracking Protection set to Strict, this protection is now rolling out gradually to all users. You can find more details about this on our support page.

    This feature is part of a progressive roll out.

    What is a progressive roll out?

    Certain new Firefox features are released gradually. This means some users will see the feature before everyone does. This approach helps to get early feedback to catch bugs and improve behavior quickly, meaning more Firefox users overall have a better experience.

Fixed

  • Increased robustness of HTTP/3 upload performance for unstable network conditions.

Changed

  • TrustPanel combines the privacy and security panels accessed from the urlbar to give the user one place to check the privacy & security settings of the current page

  • Firefox 149 tightens the security requirements for the JavaScript files that can be loaded in the parent process, to provide defense in depth against security threats.

  • On Linux, Firefox will now default to the XDG portal file picker if available, rather than the GTK3 one, which is usually better integrated with the user's desktop environment, and more powerful.

Developer

  • The toolbar of the Storage Inspector now has a button to delete all entries of the currently selected storage.

Web Platform

  • showPicker() now supports text-based <input> elements with an associated <datalist>, displaying the autofill dropdown. See documentation.

  • The functions xywh() and rect() were previously already implemented for the clip-path and offset-path properties. Now they are also available for the shape-outside property.

  • The math value of the CSS font-family is now supported and used by default for MathML's <math> element. It enables Web developers to indicate special fonts with advanced math features should be used. Firefox will rely on the serif font for mathematics defined in Firefox preferences.

  • Added support for the HTML attribute popover="hint".

  • Enabled media element pseudo-classes, such as :playing, :paused…

  • Enabled the spec-compliant HTMLMediaElement.captureStream() API.

  • Added support for closing popovers & dialogs with the Android Back Button, and implement the CloseWatcher API for handling this in script.

  • The new Reporting API provides a generic reporting mechanism for web applications to use to make reports available based on various platform features (for example Content Security Policy, Permissions-Policy, or feature deprecation reports) in a consistent manner.