Firefox 135.0

Firefox Translations now supports more languages than ever! Pages in Simplified Chinese , Japanese , and Korean can now be translated and Russian is now available as a target language for translating into.

The credit card autofill feature is now being gradually rolled out to all users globally. This feature is part of a progressive roll out. What is a progressive roll out? Certain new Firefox features are released gradually. This means some users will see the feature before everyone does. This approach helps to get early feedback to catch bugs and improve behavior quickly, meaning more Firefox users overall have a better experience.

AI Chatbot access is now being gradually rolled out to all users. To use this optional feature, choose AI Chatbot from the sidebar or from Firefox Labs . Then, complete the provider selection to see the chat interface become available on the sidebar. This feature is part of a progressive roll out. What is a progressive roll out? Certain new Firefox features are released gradually. This means some users will see the feature before everyone does. This approach helps to get early feedback to catch bugs and improve behavior quickly, meaning more Firefox users overall have a better experience.

Firefox now enforces certificate transparency , requiring web servers to provide sufficient proof that their certificates were publicly disclosed before they will be trusted. This only affects servers using certificates issued by a certificate authority in Mozilla's Root CA Program.

Additionally, the CRLite certificate revocation checking mechanism is also being gradually rolled out, substantially improving the performance of these checks. This feature is part of a progressive roll out. What is a progressive roll out? Certain new Firefox features are released gradually. This means some users will see the feature before everyone does. This approach helps to get early feedback to catch bugs and improve behavior quickly, meaning more Firefox users overall have a better experience.

Firefox now includes safeguards to prevent sites from abusing the history API by generating excessive history entries, which can make navigating with the back and forward buttons difficult by cluttering the history. This intervention ensures that such entries, unless interacted with by the user, are skipped when using the back and forward buttons.

Users on macOS and Linux are now given the option to close only the current tab if the Quit keyboard shortcut is used while multiple tabs are open in the window.

Made improvements to the Translations feature which will reduce the likelihood that models will invent new, made-up words under some circumstances.

The refreshed New Tab layout previously rolled out in Firefox 134 to users in the United States is now being made available in all countries where Stories are available. It features a repositioned logo to prioritize Web Search, Shortcuts, and Recommended Stories at the top. The update also includes changes to the card UI for recommended stories and allows users with larger screens to see up to four columns for better use of space. This feature is part of a progressive roll out. What is a progressive roll out? Certain new Firefox features are released gradually. This means some users will see the feature before everyone does. This approach helps to get early feedback to catch bugs and improve behavior quickly, meaning more Firefox users overall have a better experience.

The “Do Not Track” checkbox has been removed from preferences. If you wish to ask websites to respect your privacy, you can use the “Tell websites not to sell or share my data” setting instead. This option is built on top of the Global Privacy Control (GPC).

The "Copy Without Site Tracking" menu item was renamed to "Copy Clean Link" to help clarify expectations around what the feature does. "Copy Clean Link" is a list based approach to remove known tracking parameters from links. This option can also now be used on plain text links.

Linux binaries are now provided in XZ format , replacing the previous BZ2 format, offering faster unpacking and smaller file sizes.

Various security fixes .

Certificate Transparency is a standard for ensuring that certificates are publicly disclosed before web browsers will trust them. Firefox now supports this feature on desktop versions (but not Android). This only affects servers that use certificates issued by a certificate authority in Mozilla's Root CA Program. ( Firefox bug 1938242 ).

Developer Information

A warning is now displayed when content-visibility is used on elements where size containment does not apply.

Introduced a new console command $$$ that allows searching the page, including within shadow roots.

Enhancements to WebExtension debugging: Workers are now available in the Console panel’s context selector and breakpoints function correctly in content scripts.

With the release of Firefox 135, we are pleased to welcome the developers who contributed their first code change to Firefox in this release, 16 of whom were brand new volunteers! Please join us in thanking each of these diligent and enthusiastic individuals, and take a look at their contributions: abdoatef.ab: 1775215

commands.update can now assign keyboard shortcuts for commands to the F13 to F19 keys. However, extensions can't assign these keys from the commands manifest.json key . Users can also assign features to these keys using Manage Extension Shortcuts ( Firefox bug 1924542 )

Temporal API (Nightly release): javascript.options.experimental.temporal . 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 ).

Prioritized Task Scheduling API : dom.enable_web_task_scheduling . 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. This has temporarily been disabled in Nightly builds in order to avoid breakage in-the-wild . ( Firefox bug 1938242 ).

Added support for a post-quantum key exchange mechanism (mlkem768x25519) for HTTP/3.

The attribute values which indicate the coordinates of PointerEvent may now be fractional values rather than only integers. This allows web apps to handle the events with higher-precision coordinates when the target element is transitioned by CSS and/or the viewport is zoomed.

The behavior of mouseenter , mouseleave , pointerenter and pointerleave events was changed for improved spec compliance when the last mouseover or pointerover event target is removed.

Added support for the WebAuthn getClientCapabilities() method.

The -moz-user-input CSS property allowed you to disable input fields. The property is now deprecated and has been removed ( Firefox bug 1935198 ).

The JSON parse with source proposal is now supported, which aims 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 1934622 ). 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.

The PublicKeyCredential.getClientCapabilities() static method is supported, allowing a web app to check if a browser enables particular WebAuthn capabilities and extensions without having to resort to user agent sniffing. ( Firefox bug 1884466 ).

The mid and rid properties of the RTCOutboundRtpStreamStats interface, and the mid property of the RTCInboundRtpStreamStats interface are now supported. ( Firefox bug 1643001 ).

To make user events more realistic and better simulate real user interactions in the browser, we have moved the action sequence processing of the Perform Actions commands in both Marionette and WebDriver BiDi from the content process to the parent process. While events are still sent synchronously from the content process, they are now triggered asynchronously via IPC calls originating from the parent process ( Firefox bug 1922077 ). Due to this significant change, some regressions may still exist. If you encounter any issues, please file a bug for the Remote Agent . If the regressions block test execution, you can temporarily revert to the previous behavior by setting the Firefox preference remote.events.async.enabled to false .

With the processing of actions now handled in the parent process the following issues were fixed as well:

We now support proper queuing of action sequences without race conditions. This is particularly important for WebDriver BiDi's input.performActions command, which can be called multiple times in parallel and must execute the enqueued actions sequentially ( Firefox bug 1915798 ).

When dispatching actions, the input cancel list is now correctly updated only after the action has been successfully dispatched. Previously, if an action failed to execute, a reverse action could be left in place, leading to unexpected side effects when resetting the state of the input source ( Firefox bug 1930845 ).

When performing actions, individual actions are now retried during dispatch, particularly in situations where a single action triggers a navigation that replaces the current browsing context ( Firefox bug 1930530 , Firefox bug 1930090 ).

When performing actions, a TypeError: can't access property "getActor", browsingContext.currentWindowGlobal is null error occurred if an action (not the last one) in the action chain closed the window, and the remaining actions were still being dispatched ( Firefox bug 1932916 ).

Some Marionette and WebDriver BiDi commands that rely internally on a requestAnimationFrame being emitted before returning would hang if the current browsing context was navigated during their execution ( Firefox bug 1937118 ).

Added support for the format field in the browsingContext.captureScreenshot command, allowing clients to specify different file formats ( image/png and image/jpeg are currently supported) and define the compression quality for screenshots ( Firefox bug 1861737 ).