MDN self-hosted library · e01.org

Firefox 150 release notes for developers

This article provides information about the changes in Firefox 150 that affect developers. Firefox 150 was released on April 21, 2026.

no runnable cells firefox-release-notes upstream source

This article provides information about the changes in Firefox 150 that affect developers. Firefox 150 was released on April 21, 2026.

Changes for web developers

Developer Tools

  • A specific message is now displayed in the Response tab of the Network pane to indicate why there is no response data when a request has been redirected. (Firefox bug 2016679).
  • A new "Element-specific pseudo-classes" section has been added to the pseudo-class toggle pane, including a toggle for the :open pseudo-class, which is only available for elements that have an open state like <dialog> elements. The existing toggle for the :visited pseudo-class was also moved there, as it only applies to <a> and <area> elements. (Firefox bug 2014442).

HTML

  • The "auto" keyword is now supported as an option for the sizes attribute of <img> elements (and HTMLImageElement.sizes). This allows lazy-loaded <img> elements to use the calculated image layout size, after any CSS has been applied, to select which image to display from a srcset. This is simpler than specifying media conditions and their associated sizes in the attribute, which likely duplicates behavior that is already captured in CSS media queries. (Firefox bug 1819581).

CSS

  • The color-mix() CSS function now accepts multiple <color> values, rather than just two. This allows you to mix any number of colors. (Firefox bug 2024171).

  • The light-dark() CSS function now accepts <image> values. This allows using images, gradients, and so on for different color schemes. (Firefox bug 2023569).

  • The media-based pseudo-classes :buffering, :muted, :paused, :playing, :seeking, :stalled, and :volume-locked are now supported. They allow you to style audio and video elements based on their current state, such as playing or paused. (Firefox bug 2020775).

  • The revert-rule CSS keyword is now supported. It allows a property's value to be determined as if the current style rule had not been present, so that the value from another matching rule can take effect instead. (Firefox bug 2017307).

  • The overscroll-behavior CSS property (and its longhand properties overscroll-behavior-x, overscroll-behavior-y, overscroll-behavior-block, and overscroll-behavior-inline) now correctly apply to scroll containers that have no scrollable overflow, such as elements with overflow: hidden. Previously, the property was ignored on such elements. (Firefox bug 1837436).

JavaScript

No notable changes.

APIs

  • The Sanitizer.replaceElementWithChildren() method will now return false if the element to be replaced is html in the HTML namespace. In other words, you can't use this method to create a Sanitizer that will replace the <html> element with its inner content. (Firefox bug 2022176).

  • The scrollend event is now supported on VisualViewport, allowing elements to be updated when a scrolling action is completed. This might be used, for example, to unhide or otherwise adjust the position of fixed UI elements once a user finishes panning around a pinch-zoomed screen. (Firefox bug 1801658).

DOM

  • The options.shadowRoots argument of the Document.caretPositionFromPoint() method is now supported. This allows the method to return the node containing the caret from within a shadow DOM, provided its associated ShadowRoot was passed as an option. (Firefox bug 1914596).

  • The HighlightRegistry.highlightsFromPoint() method is now supported, providing a mechanism for web pages to get information about all the CSS custom highlights applied at a particular point. This includes highlights that are inside shadow roots, provided the associated ShadowRoot instance was passed to the method. (Firefox bug 1917991).

  • The CSSFontFaceDescriptors interface is now supported, and an instance of this type is returned by the CSSFontFaceRule.style property. (Firefox bug 2019904).

  • The non-standard caretRangeFromPoint() method of the Document interface is now supported. (Firefox bug 1550635).

  • The ariaNotify() method is now supported on Document and Element. This queues a string of text to be announced by a screen reader, providing a more ergonomic and reliable alternative to ARIA live regions. (Firefox bug 2018095).

Media, WebRTC, and Web Audio

WebDriver conformance (WebDriver BiDi, Marionette)

General

  • Fixed an issue where having pending downloads when closing the browser could be blocked by a prompt. The prompt is now dismissed automatically. (Firefox bug 2003840).

WebDriver BiDi

  • Added the emulation.setNetworkConditions command, which supports the type: offline at the moment. Using this, you can emulate offline mode either on specific browsing contexts, on user contexts (a.k.a. containers) or globally. (Firefox bug 1993079).
  • Improved our support for non utf-8 header values across all the network module commands and events. They are now properly serialized to BytesValue. (Firefox bug 1994996).
  • Fixed a bug for download events triggered by a response with the "Content-Disposition" header. Such events were missing the navigation property if the download was initiated by a link with target="_blank". (Firefox bug 1999481).
  • Updated the log.entryAdded event to only be emitted for console API calls that actually print a message in browser developer tools (see also the console specification: using the printer). With this change, using console.clear or console.time no longer triggers an event. (Firefox bug 1866749).
  • Fixed a race condition with the browsingContext.setViewport command which could timeout if several contexts were created in parallel. (Firefox bug 2019511).
  • Improved the browsingContext.locateNodes command to allow retrieving the HTML element (documentElement) of a page when using the css locator. (Firefox bug 2020578).

Marionette

  • Fixed the WebDriver:getShadowRoot command to stop returning user-agent shadow roots. (Firefox bug 2016741).

Changes for add-on developers

Experimental web features

These features are shipping in Firefox 150 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.

  • Namespaced attributes in attr() CSS function: layout.css.attr.enabled

The attr CSS function now accepts namespaced attributes. This allows you to take attributes from elements of XML-based languages, such as SVG and style them accordingly. (Firefox bug 2014060)

  • @container style() queries (Nightly): layout.css.style-queries.enabled

The @container CSS at-rule supports style() queries. This has been updated to support the nesting of style() queries. (Firefox bug 2014098).

  • Absolutely positioned elements in multi-column containers and when printing: layout.abspos.fragmentainer-aware-positioning.enabled

Absolutely positioned elements inside multi-column containers and when printing are now correctly positioned and fragmented. This improves interoperability with other browsers and prevents layout issues such as overlapping text or content loss. (Firefox bug 2018797).

  • Scoped custom element registries: dom.scoped-custom-element-registries.enabled

The customElementRegistry property is supported on Document, Element, and ShadowRoot. This allows the definition of scoped custom element registries. (Firefox bug 2018900).

  • Multiple import maps: dom.multiple_import_maps.enabled

Multiple import maps give developers more flexibility when structuring and loading JavaScript modules. (Firefox bug 1916277).