MDN self-hosted library · e01.org

Firefox 145 release notes for developers

This article provides information about the changes in Firefox 145 that affect developers. Firefox 145 was released on November 11, 2025.

no runnable cells firefox-release-notes upstream source

This article provides information about the changes in Firefox 145 that affect developers. Firefox 145 was released on November 11, 2025.

Changes for web developers

HTML

No notable changes.

CSS

  • The text-autospace property is now supported, allowing automatic spacing adjustments between characters from different scripts (Firefox bug 1981086, Firefox bug 1869577).

  • The math generic font family is now supported as a value of the font-family property, allowing mathematical expressions to use appropriate fonts. (Firefox bug 1788937).

  • Separators can appear in select menus since hr in <select> was implemented. These are now also supported in Firefox for Android. (Firefox bug 1867045, Firefox bug 1830909).

JavaScript

  • Firefox now supports the Atomics.waitAsync() static method, which allows synchronization of threads based upon the value in a shared memory location. The method waits asynchronously for the value and returns an object representing the operation's result. It is non-blocking and usable on the main thread. (Firefox bug 1884148).

HTTP

Security

  • When Bounce Tracking Protection (BTP) is enabled, it now runs in "stateless" mode by default. In "stateless" mode, the browser no longer only flags sites that are part of a "bounce" that set state information (such as a cookie); it flags all sites that are part of a "bounce". See Bounce tracking mitigations for more information on how BTP works. (Firefox bug 1990831).

APIs

  • The source property of the ToggleEvent interface is now supported. If a popover is triggered to open or close by an HTML element such as a button, the event's source property will contain the element that triggered the popover. (Firefox bug 1968987).
  • A CSSStyleProperties instance is now returned for the style property on HTMLElement, MathMLElement, SVGElement, and CSSStyleRule, and the Window.getComputedStyle() method. Previously a CSSStyleDeclaration instance was returned. (Firefox bug 1989925)

Media, WebRTC, and Web Audio

  • RTCEncodedVideoFrame and RTCEncodedAudioFrame are now serializable objects, and RTCEncodedAudioFrame() and RTCEncodedVideoFrame() copy constructors are supported. These changes allow frames to be cloned, and to be shared between workers and the main thread. (Firefox bug 1868223 and Firefox bug 1975032).

  • The Matroska container (.mkv) is now supported for the most commonly-used codecs: AVC, HEVC, VP8, VP9, AV1, AAC, Opus, and Vorbis. (Firefox bug 1991752).

WebDriver conformance (WebDriver BiDi, Marionette)

WebDriver BiDi

  • Implemented the emulation.setUserAgentOverride command, which allows you to override the user-agent string used by the browser either for a set of contexts, user contexts or globally. (Firefox bug 1987935).
  • Implemented the browsingContext.downloadEnd event, which is emitted when a download finishes (whether it is successful or canceled) (Firefox bug 1970293).
  • Updated the destination property of the network.beforeRequestSent event to document for top-level navigations. (Firefox bug 1985552).
  • Updated the browsingContext download events to reuse the same navigation id as the previous browsingContext.navigationStarted event. (Firefox bug 1986938).
  • Fixed a bug for network data collection, where non-ASCII characters in response bodies were not properly encoded. (Firefox bug 1986022).
  • Fixed a bug with the network.getData command, which would fail requests with an empty response body. (Firefox bug 1986025).
  • Fixed a bug where some network events could be flagged as blocked even if they were not. (Firefox bug 1989919).

Changes for add-on developers

  • Cookies created with cookies.set() are now validated, and invalid cookies are rejected. This change was implemented in Nightly only from Firefox 142. (Firefox bug 1976509)

Experimental web features

These features are shipping in Firefox 145 but are disabled by default. To experiment with them, search for the appropriate preference on the about:config page and set it to true. You can find more such features on the Experimental features page.

  • CSS anchor positioning (Nightly): layout.css.anchor-positioning.enabled

Nightly builds now support CSS anchor positioning by default, which allows you to tether elements together. The anchor-positioned elements can then have their size and position set relative to the size and location of the anchor elements to which they are bound. (General: Firefox bug 1988224, position-area: Firefox bug 1924086, custom @position-try fallbacks: Firefox bug 1962598).

  • CSS module scripts: (Nightly) and layout.css.module-scripts.enabled.

CSS module scripts are now supported, allowing a stylesheet to be loaded into a script as a CSSStyleSheet instance using the import keyword and the type import attribute set to type="css". (Firefox bug 1720570).

  • text-decoration-trim: layout.css.text-decoration-trim.enabled

The CSS text-decoration-trim property is supported but currently disabled by default. It allows you to specify text-decoration start and end offsets to shorten, lengthen, or shift the position of text decorations with respect to the text (Firefox bug 1979915).

  • Trusted Types API for scripts (Nightly/Early Beta): dom.security.trusted_types.enabled

The Trusted Types API is now enabled in early beta releases. (Firefox bug 1976656).

The changes include:

  • Addition of the TrustedTypePolicyFactory, TrustedTypePolicy, TrustedHTML, TrustedScript, TrustedScriptURL interfaces, and the trustedTypes property on Window and WorkerGlobalScope.
  • Updates to injection sink interfaces APIs, such as Element.innerHTML and document.write(), to allow the TrustedHTML, TrustedScript, TrustedScriptURL to be passed as well as strings.
  • Support for the require-trusted-types-for and trusted-types directives, and the 'trusted-types-eval' keyword, of the Content-Security-Policy HTTP header. These can be used to enforce trusted types instead of strings, name the specific policies that are allowed, and to enable eval() and similar functions to be used when Trusted Types are supported and enforced.

  • Storage Access headers (Nightly): dom.storage_access.headers.enabled. The Sec-Fetch-Storage-Access and Activate-Storage-Access HTTP headers are now supported, enabling a more efficient Storage Access API workflow. (Firefox bug 1991688).