Firefox 132 for developers

No notable changes

• The text-emphasis-position property now supports the auto value to bring it inline with text-underline-position (Firefox bug 1919658).

Removals

• The -moz-user-modify CSS property has been removed. This property has been deprecated in favour of the contenteditable global attribute. (Firefox bug 1920118).

• The (?ims-ims:...) regular expression modifiers allow you to make changes to only take effect in a specific part of a regex pattern. (Firefox bug 1913752 & Firefox bug 1899813).

Removals

• HTTP/2 Server Push is deactivated by default with the preference network.http.http2.allow-push now set to false. This feature is no longer supported by any other major browser, and the implementation may be completely removed in a future release. (Firefox bug 1915848).

• All third-party cookies are now blocked in Strict Enhanced Tracking Protection. (Firefox bug 1918037).

• The drawingBufferColorSpace and unpackColorSpace properties of the WebGLRenderingContext and WebGL2RenderingContext interfaces are now supported. These specify the color space of the WebGL drawing buffer, and the color space to convert to when importing textures, respectively. (Firefox bug 1885491, Firefox bug 1885446).
• The Notification.silent property is now supported, which controls whether system notifications should be silent. When silent: true is specified in the Notification() constructor, the resulting system notification is issued without accompanying sounds or vibrations, regardless of device settings (Firefox bug 1809028).
• The fetchpriority attribute of the <link>, <script>, and <img> elements, the fetchPriority property of the HTMLLinkElement, HTMLScriptElement, and HTMLImageElement interfaces, the options.priority parameter passed to the Request() constructor, and the fetchpriority directive in the HTTP Link header, are now supported. These allow developers to provide a hint about the relative priority for fetching a particular resource compared to other resources of the same type, and can be used alongside other ways of setting the priority, such as preloading. (Firefox bug 1854077).

Media, WebRTC, and Web Audio

• The requestVideoFrameCallback() and cancelVideoFrameCallback() methods of the HTMLVideoElement interface are now supported. The requestVideoFrameCallback() registers a callback function that runs when a new video frame is sent to the compositor. Developers can use this function to perform operations on each video frame, enabling more efficient painting to a canvas, video analysis, synchronization with external audio sources, and so on. The method returns a callback handle that can be passed to cancelVideoFrameCallback() in order to cancel the outstanding callback request. (Firefox bug 1919367, Firefox bug 1800882).
• The MediaStreamTrack.getCapabilities() method is now supported. This returns an object detailing the accepted values or value range for each constrainable property of the associated MediaStreamTrack (Firefox bug 1179084).

WebDriver BiDi

• Implemented several improvements to make WebDriver BiDi commands more reliable when used during navigation or with newly created tabs. Previously commands such as browsingContext.setViewport were likely to fail due to an AbortError, they will now be retried a few times to avoid such issues. (Firefox bug 1854942, Firefox bug 1918287, Firefox bug 1918672, Firefox bug 1921756)
• The browsingContext.contextCreated event is now correctly emitted for lazy-loaded frames. Previously the event would only be emitted when the iframe actually started loading its content. (Firefox bug 1878166)
• Network events are now correctly emitted for cached stylesheet requests. (Firefox bug 1879438)
• Network event timings were previously using the wrong unit and were provided in microseconds. They are now correctly set in milliseconds. (Firefox bug 1916685)
• The requestTime from network event timings should now be more accurate and really match the time where the request actually started. (Firefox bug 1922390)

These features are newly shipped in Firefox 132 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.

• Cookie Store API: dom.cookieStore.enabled.

  The Cookie Store API is a modern, Promise-based method of managing cookies that does not block the event loop and does not rely on Document (it can therefore be made available to service workers). As of Firefox 132, a subset of the Cookie Store API has been implemented. (Firefox bug 1800882). This includes:

  • The CookieStore interface, but partitioned is not included in return values.
  • The CookieChangeEvent interface, excluding partitioned properties.
  • The Window.cookieStore property.
  • The ServiceWorkerGlobalScope.cookieStore property.

• The fetch() keepalive option: dom.fetchKeepalive.enabled.

  The global fetch() method has a keepalive initialization option. When keepalive is set to true, the browser will not abort the associated request if the page that initiated it is unloaded before the request is complete.

  This enables a fetch request to function as an alternative to Navigator.sendBeacon() when sending analytics at the end of a session, which has some advantages (you can use HTTP methods other than POST, customize request properties, and access the server response via the fetch Promise fulfillment). It is also available in service workers. (Firefox bug 1906952).

• CloseWatcher: dom.closewatcher.enabled. The CloseWatcher interface enables developers to implement components that can be closed using device-native mechanisms, in the same way as built-in components. For example, on Android you can close a dialog using the back button: this interface allows you to similarly close a custom sidebar. (Firefox bug 1888729).

• Promise.try(): javascript.options.experimental.promise_try. Promise.try() is a convenience method that takes a callback of any kind (returns or throws, synchronously or asynchronously) and wraps its result in a Promise so that promise semantics (e.g. .then(), .catch()) can be used to handle it (Firefox bug 1905364).

• JSON.parse with source: javascript.options.experimental.json_parse_with_source. The JSON.parse source text access proposal extends JSON.parse behavior to provide features to mitigate issues around loss of precision when converting values such as large floats and date values between JavaScript values and JSON text (Firefox bug 1913085, Firefox bug 1925334). Specifically, the following features are now available:

  • The JSON.parse() reviver parameter context argument: Provides access to the original JSON source text that was parsed.
  • JSON.isRawJSON(): Tests whether a value is an object returned by JSON.rawJSON().
  • JSON.rawJSON(): Creates a "raw JSON" object containing a piece of JSON text, which can then be included in an object to preserve the specified value when that object is stringified.