Firefox 161 release notes for developers (Beta)
This article provides information about the changes in Firefox 161 that affect developers. Firefox 161 is the current Beta version of Firefox and ships on November 24, 2026.
Note: The release notes for this Firefox version are still a work in progress.
Changes for web developers
SVG
- The
referrerpolicyattribute is now supported on the<image>,<script>, and<feImage>elements, along with the correspondingSVGImageElement.referrerPolicy,SVGScriptElement.referrerPolicy, andSVGFEImageElement.referrerPolicyproperties. These control how much referrer information is sent in theRefererheader when the element fetches the resource referenced by itshrefattribute. This works in the same way as thereferrerpolicyattribute on the HTML<img>and<script>elements. (Firefox bug 2079321).
CSS
- The
random()CSS function is now supported. It generates a random value within a specified range and can optionally limit the possible values to increments of a specified step size. An optional<random-key>parameter can be used to share a random base value acrossrandom()functions, for example on different elements or in different properties. (Firefox bug 2072252).
APIs
-
The
anticipatedConcurrentIncomingUnidirectionalStreamsandanticipatedConcurrentIncomingBidirectionalStreamsproperties of theWebTransportinterface are now supported, along with the correspondingoptionsproperties that can be used to set them in theWebTransport()constructor. These properties represent the maximum number of incoming unidirectional and bidirectional streams, respectively, that the application expects the server to have open at the same time. (Firefox bug 2007825). -
The Clipboard API now supports custom clipboard formats, which allow web apps to write and read their own data formats using
Clipboard.write()andClipboard.read(). A custom format is a MIME type prefixed with"web ", such as"web text/x-my-format". Custom formats can only be read by a page that is same-origin with the page that wrote them. (Firefox bug 2053725, Firefox bug 2086505). -
The
NavigationTransition.toproperty of the Navigation API is now supported. This returns aNavigationDestinationfor the ongoing navigation, so code outside thenavigateevent handler can find out where the navigation is going. For example, anavigateerrorhandler can use it to report which navigation failed. (Firefox bug 1991959).
Media, WebRTC, and Web Audio
- The
RTCRtpSender.setParameters()method now supports the optionalsetParameterOptionsparameter. This lets you ask the encoder for an encoding to generate a key frame in the same call that you use to change the sender's encoding parameters, such asactiveorscaleResolutionDownBy. Receivers can then avoid requesting a key frame after the change. (Firefox bug 2057265).
Changes for add-on developers
Experimental web features
These features are shipping in Firefox 161 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.
-
Cross-document view transitions (Nightly):
dom.viewTransitions.cross-document.enabledCross-document view transitions are now enabled by default in Nightly. These can be used to animate the transition between same-origin pages in a multi-page app. (Firefox bug 2084340).
-
Render blocking (Nightly):
dom.element.blocking.enabledThe
blocking="render"attribute of the<link>,<script>, and<style>elements is now enabled by default in Nightly. This lets you block rendering of the page until the marked stylesheet has loaded or script has run, so the page doesn't first appear unstyled or incomplete. (Firefox bug 2084340).