Experimental features in Firefox

Layout for input type="search" has been updated. This causes a search field to have a clear icon once someone starts typing in it, to match other browser implementations. (See Firefox bug 558594 for more details.)

HTML password input elements (<input type="password">) include an "eye" icon that can be toggled to display or obscure the password text (Firefox bug 502258).

This feature renders control characters (Unicode category Cc) other than tab (U+0009), line feed (U+000A), form feed (U+000C), and carriage return (U+000D) as a hex box when they are not expected. (See Firefox bug 1099557 for more details.)

The initial-letter CSS property is part of the CSS Inline Layout specification and allows you to specify how dropped, raised, and sunken initial letters are displayed. (See Firefox bug 1223880 for more details.)

The fit-content() function as it applies to width and other sizing properties. This function is already well-supported for CSS Grid Layout track sizing. (See Firefox bug 1312588 for more details.)

Earlier called "scroll-linked animations", a scroll-driven animation depends on the scroll position of a scrollbar instead of time or some other dimension. The scroll-timeline-name and scroll-timeline-axis properties (and the scroll-timeline shorthand property) allow you to specify that a particular scrollbar in a particular named container can be used as the source for a scroll-driven animation. The scroll timeline can then be associated with an animation by setting the animation-timeline property to the name value defined using scroll-timeline-name.

When using the scroll-timeline shorthand property, the order of the property values must be scroll-timeline-name followed by scroll-timeline-axis. The longhand and shorthand properties are both available behind the preference.

You can alternatively use the scroll() functional notation with animation-timeline to indicate that a scrollbar axis in an ancestor element will be used for the timeline.

For more information, see Firefox bug 1807685, Firefox bug 1804573, Firefox bug 1809005, Firefox bug 1676791, Firefox bug 1754897, Firefox bug 1817303, and Firefox bug 1737918.

The timeline-scope, animation-range-start and animation-range-end properties (and the animation-range shorthand property) are not yet supported. For more information, see Firefox bug 1676779.

The @scope CSS at-rule allows you to select specific child elements without having to overly increase the specificity of CSS selectors (Firefox bug 1886441).

The CSS font-variant-emoji property allows you to set a default presentation style for displaying emojis. See (Firefox bug 1461589) for more details.

The CSS prefers-reduced-transparency media feature lets you detect if a user has enabled the setting to minimize the amount of transparent or translucent layer effects on their device. See (Firefox bug 1736914) for more details.

The CSS inverted-colors media feature lets you detect if a user agent or the underlying operating system is inverting colors. See (Firefox bug 1794628) for more details.

The CSS view-timeline-name property lets you give a name to particular element, identifying that its ancestor scroller element is the source of a view progress timeline. The name can then be assigned to the animation-timeline, which then animates the associated element as it moves through the visible area of its ancestor scroller. See (Firefox bug 1737920) for more details.

The CSS view() function lets you specify that the animation-timeline for an element is a view progress timeline, which will animate the element as it moves through the visible area of its ancestor scroller. The function defines the axis of the parent element that supplies the timeline, along with the inset within the visible area at which the animation starts and begins. See (Firefox bug 1808410) for more details.

The -moz- prefixed CSS transform properties can be disabled by setting the layout.css.prefixes.transforms preference to false. The intent is to disable these once the standard CSS zoom properties are well supported. (Firefox bug 1886134, Firefox bug 1855763).

Specifically, this preference will disable the following prefixed properties:

• -moz-backface-visibility
• -moz-perspective
• -moz-perspective-origin
• -moz-transform
• -moz-transform-origin
• -moz-transform-style

The <h1> heading doesn't decrease in font size now when nested within sectioning elements <article>, <aside>, <nav>, and <section>. The UA styles for <h1> nested within sectioning elements are no longer relevant since the outline algorithm has been removed from the HTML specification. (Firefox bug 1883896).

The CSS shape() function is a <basic-shape> data type that enables you to define a shape in the clip-path and offset-path properties using one or more "shape commands". These commands are very similar to the SVG path commands. The shape() function is similar in some respects to the path() function, but unlike path(), which uses the SVG path syntax, shape() uses standard CSS syntax. This enables you to easily create and edit shapes and also allows the use of CSS math functions. For more details, see Firefox bug 1823463 for the shape() function support in clip-path, Firefox bug 1884424 for the function's support in offset-path, and Firefox bug 1884425 for its interpolation support.

The CSS letter-spacing property now splits the specified letter spacing evenly on both sides of each character. This is unlike the current behavior where spacing is added primarily to one side. This approach can improve text spacing, especially in mixed-directional text Firefox bug 1891446.

The CSS calc() function can now parse color channels in relative colors, allowing you to correctly calculate changes to colors in different color spaces or while using different functional notations Firefox bug 1889561.

The CSS Anchor Positioning module defines a number of features that allow elements to be defined as anchor elements, and for other elements to be positioned relative to anchor elements. This allows, for example, tooltips to be displayed alongside associated content as it scrolls through the viewport, moving as needed when it would overflow the viewport, and disappearing when the anchor moves offscreen. The set of features are being progressively rolled out behind a preference (Firefox bug 1838746).

The parts that have been implemented include:

• CSSPositionTryRule and CSSPositionTryDescriptors (Firefox 131).

The CSS ::details-content pseudo-element enables you to style the content of the <details> element (Firefox bug 1901037).

The <discard> SVG element is now supported, along with its corresponding SVGDiscardElement JavaScript interface. The element allows developers to specify a trigger time or event at which a specified element and its children should be removed from the DOM. An SVG viewer can use this information to conserve memory by discarding elements that are no longer needed, such as animated elements that have completed. (Firefox bug 1069931).

The Temporal object aims to simplify working with dates and times in various scenarios, with built-in time zone and calendar representations (Firefox bug 1912511). This includes:

• A duration (difference between two time points): Temporal.Duration
• Points in time:
  • As a unique instant in history:
    • A timestamp: Temporal.Instant
    • A date-time with a time zone: Temporal.ZonedDateTime
  • Time-zone-unaware date/time ("Plain"):
    • Date (year, month, day) + time (hour, minute, second, millisecond, nanosecond): Temporal.PlainDateTime
      • Date (year, month, day): Temporal.PlainDate
        • Year, month: Temporal.PlainYearMonth
        • Month, day: Temporal.PlainMonthDay
      • Time (hour, minute, second, millisecond, nanosecond): Temporal.PlainTime
• Now (current time) as various class instances, or in a specific format: Temporal.Now

Built-in web components with "open" and "close" semantics, such as modal dialogs and popovers, can be closed using device-native mechanisms. For example, on Android you can close a dialog using the back button. The CloseWatcher interface allows developers to implement UI components, such as custom sidebars, that can similarly be closed using native mechanisms. (Firefox bug 1888729).

The Trusted Types API provides mechanisms to ensure that functions that can potentially be used as vectors for XSS attacks are only able to be called with data that has been validated or sanitized.

This subset of the API has been implemented:

• TrustedTypePolicyFactory:
  • getAttributeType() and getPropertyType() (Firefox bug 1917783, Firefox bug 1917784).
• The write() and writeln() methods of the Document interface now accept TrustedHTML objects as parameters, in addition to strings. (Firefox bug 1906301).
• The text, innerText, and textContent properties of the HTMLScriptElement interface now accept TrustedScript objects a value, while src accepts TrustedScriptURL values. (Firefox bug 1905706).
• The Window.setInterval() and Window.setTimeout() methods can be called with a TrustedScript. (Firefox bug 1931290).
• The global trustedTypes property is available for accessing the Trusted Types API.
• The properties Element.innerHTML and ShadowRoot.innerHTML can be called with trusted types.

MutationEvent and its associated events (DOMSubtreeModified, DOMNodeInserted, DOMNodeRemoved, DOMCharacterDataModified, DOMAttrModified) are on the path for removal, and have been disabled on nightly. (Firefox bug 1951772).

The actions read-only property of the Notification interface is supported in Nightly. This contains notification actions set with ServiceWorkerRegistration.showNotification(). (Firefox bug 1225110).

WebGL: Draft extensions

When this preference is enabled, any WebGL extensions currently in "draft" status which are being tested are enabled for use. Currently, there are no WebGL extensions being tested by Firefox.

WebGPU API

The WebGPU API provides low-level support for performing computation and graphics rendering using the Graphics Processing Unit (GPU) of the user's device or computer. See Firefox bug 1602129 for our progress on this API.

The Reporting API now has support for reporting Content Security Policy (CSP) violations.

Report instances returned by the ReportingObserver interface can now have a type value of "csp-violation" and a body property that contains an instance of the CSPViolationReportBody interface. This allows CSP violations to be reported within a web page.

CSP violation reports can also be sent to remote endpoints that are specified by name in the CSP report-to directive — endpoints names and corresponding URLs must first be defined in the Reporting-Endpoints or Report-To HTTP response headers. The report is a serialization of the Report object described above, with a body property that is a serialization of an CSPViolationReportBody instance.

This violation report replaces a similar CSP-specific mechanism for sending violation reports, which uses the CSP report-uri directive to set the URL of the reporting endpoint, and has a CSP-specific JSON violation report format. (Firefox bug 1391243).

The following experimental features include those found in the WebRTC API, the Web Audio API, the Media Source Extensions API, the Encrypted Media Extensions API, and the Media Capture and Streams API.

Asynchronous SourceBuffer add and remove

This adds the promise-based methods appendBufferAsync() and removeAsync() for adding and removing media source buffers to the SourceBuffer interface. See Firefox bug 1280613 and Firefox bug 778617 for more information.

AVIF compliance strictness

The image.avif.compliance_strictness preference can be used to control the strictness applied when processing AVIF images. This allows Firefox users to display images that render on some other browsers, even if they are not strictly compliant.

Permitted values are:

• 0: Accept images with specification violations in both recommendations ("should" language) and requirements ("shall" language), provided they can be safely or unambiguously interpreted.
• 1 (default): Reject violations of requirements, but allow violations of recommendations.
• 2: Strict. Reject any violations in requirements or recommendations.

JPEG XL support

Firefox supports JPEG XL images if this feature is enabled. See Firefox bug 1539075 for more details.

Note that, as shown below, the feature is only available on Nightly builds (irrespective of whether the preference is set).

The CSS Custom Highlight API provides a mechanism for styling arbitrary text ranges in a document (generalizing the behavior of other highlight pseudo-elements such as ::selection, ::spelling-error, ::grammar-error, and ::target-text). The ranges are defined in JavaScript using Range instances grouped in a Highlight, and then registered with a name using HighlightRegistry. The CSS ::highlight pseudo-element is used to apply styles to a registered highlight. See Firefox bug 1703961 for more details.

WebVR API (Disabled)

The deprecated WebVR API is on the path for removal. It is disabled by default on all builds Firefox bug 1750902.

Selections crossing shadow DOM boundary

The Selection.getComposedRanges() method can be used to get an array of StaticRange objects representing the current selected range or ranges. Unlike Selection.getRangeAt(), this method can return ranges with anchor or focus nodes inside a shadow DOM, but only if it is passed the ShadowRoot objects that contain those nodes. Otherwise, it will return a range that has been re-scoped to include the host node of the shadow root that contains the node. The Selection methods setBaseAndExtent(), collapse(), and extend() have also been modified to accept nodes inside a shadow root.

User selection via mouse, keyboard, and so on, can start and end anywhere in the document, including inside any open or closed shadow trees. (Firefox bug 1867058).

HTMLMediaElement properties: audioTracks and videoTracks

Enabling this feature adds the HTMLMediaElement.audioTracks and HTMLMediaElement.videoTracks properties to all HTML media elements. However, because Firefox doesn't currently support multiple audio and video tracks, the most common use cases for these properties don't work, so they're both disabled by default. See Firefox bug 1057233 for more details.

GeometryUtils methods: convertPointFromNode(), convertRectFromNode(), and convertQuadFromNode()

The GeometryUtils methods convertPointFromNode(), convertRectFromNode(), and convertQuadFromNode() map the given point, rectangle, or quadruple from the Node on which they're called to another node. (See Firefox bug 918189 for more details.)

GeometryUtils method: getBoxQuads()

The GeometryUtils method getBoxQuads() returns the CSS boxes for a Node relative to any other node or viewport. (See Firefox bug 917755 for more details.)

Primary payment handling

The Payment Request API provides support for handling web-based payments within web content or apps. Due to a bug that came up during testing of the user interface, we have decided to postpone shipping this API while discussions over potential changes to the API are held. Work is ongoing. (See Firefox bug 1318984 for more details.)

The Web Share API allows sharing of files, URLs and other data from a site. This feature is enabled on Android in all builds, but behind a preference on Desktop (unless specified below).

ScreenOrientation.lock()

The ScreenOrientation.lock() method allows a device to be locked to a particular orientation, if supported by the device and allowed by browser pre-lock requirements. Typically locking the orientation is only allowed on mobile devices when the document is being displayed full screen. See Firefox bug 1697647 for more details.

The Prioritized Task Scheduling API provides a standardized way to prioritize all tasks belonging to an application, whether they defined in a website developer's code, or in third party libraries and frameworks. (Firefox bug 1734997)

This feature was enabled on Firefox Nightly in Firefox 101. Support in Firefox Nightly 135 has been temporarily disabled in order to avoid breakage in-the-wild.

Notifications have the requireInteraction property set to true by default on Windows systems and in the Nightly release (Firefox bug 1794475).

In order to help mitigate man-in-the-middle (MitM) attacks caused by Flash content on encrypted pages, a preference has been added to treat OBJECT_SUBREQUESTs as active content. See Firefox bug 1190623 for more details.

The two security.insecure_connection_text_* preferences add a "Not secure" text label in the address bar next to the traditional lock icon when a page is loaded insecurely (that is, using HTTP rather than HTTPS). The browser.urlbar.trimHttps preference trims the https: prefix from address bar URLS. See Firefox bug 1853418 for more details.

Permissions Policy allows web developers to selectively enable, disable, and modify the behavior of certain features and APIs in the browser. It is similar to CSP but controls features instead of security behavior. This is implemented in Firefox as Feature Policy, the name used in an earlier version of the specification.

Note that supported policies can be set through the allow attribute on <iframe> elements even if the user preference is not set.

PPA API provides an alternative to user tracking for ad attribution using the new navigator.privateAttribution object with saveImpression() and measureConversion() methods. Read more about PPA in the explainer. This experiment can be enabled for websites via origin trial or in the browser by setting the preference to 1. (Firefox bug 1900929).

The HTTP Accept header in default requests and image requests can be configured via a preference to indicate support for the image/jxl MIME type.

SameSite cookies have a default value of Lax. With this setting, cookies are only sent when a user is navigating to the origin site, not for cross-site subrequests to load images or frames into a third party site and so on. For more details see Firefox bug 1617609.

The Access-Control-Allow-Headers is a response header to a CORS preflight request, that indicates which request headers may be included in the final request. The response directive can contain a wildcard (*), which indicates that the final request may include all headers except the Authorization header.

By default, Firefox includes the Authorization header in the final request after receiving a response with Access-Control-Allow-Headers: *. Set the preference to false to ensure Firefox does not include the Authorization header. For more details see Firefox bug 1687364.

The Clear-Site-Data can be used with the cache or * directives to clear the local browser cache. For more details see Firefox bug 1942272.

Mozilla's developer tools are constantly evolving. We experiment with new ideas, add new features, and test them on the Nightly and Developer Edition channels before letting them go through to beta and release. The features below are the current crop of experimental developer tool features.

• Firefox developer release notes
• Firefox Nightly
• Firefox Developer Edition