This release of Chrome had 12 new features.
Enables web applications with the window-management permission to maximize(), minimize(), and restore() their windows, and to prevent resizing through setResizable(). Additionally, new CSS media features display-state and resizable enable scripts and content to adapt to the respective window states and resizability. These features improve the usability of VDI remote application windows in Web clients, especially when it comes to titlebar window controls. The new functionality enhances existing Window Management API features: https://chromestatus.com/feature/5252960583942144 #
This feature was specified in this Spec.
Samples: https://awc-demo-4a08a808.web.app/
Add post-quantum cryptography and a common symmetric AEAD to the set of cryptographic algorithms available in the Web Cryptography API. This will enable developers to have access browser-provided implementations of common quantum-resistant cryptographic algorithms standardized by NIST. * ML-KEM - 768, 1024 * ML-DSA - 44, 65, 87 * ChaCha20-Poly1305 * X-Wing #
This feature was specified in this Spec.
The CSS symbols() function lets authors define a counter style inline instead of first declaring a named @counter-style at-rule. It builds an anonymous counter style from a list of string symbols plus an optional counting system (cyclic, numeric, alphabetic, symbolic, or fixed), and is accepted as the counter style in list-style-type, the list-style shorthand, and counter() / counters(). #
This feature was specified in this Spec.
Samples: https://developer.mozilla.org/en-US/docs/Web/CSS/symbols
The text-decoration-skip-spaces CSS property controls whether text decoration lines (underlines, overlines, line-throughs, etc.) skip over whitespace characters. This allows authors to prevent decorations from being drawn under spaces, which is often more visually appealing. #
This feature was specified in this Spec.
Samples: http://wpt.live/css/css-text-decor/text-decoration-skip-spaces-001.htmlhttp://wpt.live/css/css-text-decor/text-decoration-skip-spaces-002.htmlhttp://wpt.live/css/css-text-decor/text-decoration-skip-spaces-003.htmlhttp://wpt.live/css/css-text-decor/text-decoration-skip-spaces-004.html
This Web Platform feature enables issuing websites (e.g., a university, government agency, or bank) to securely initiate the provisioning (issuance) process of digital credentials directly into a user's mobile wallet application. On Android, this capability leverages the Android IdentityCredential CredMan system (Credential Manager). On Desktop, it leverages cross-device approaches using the CTAP protocol similar to Digital Credentials presentation. #
This feature was specified in this Spec.
### Update (November 4, 2026): Feature rollback Based on customer feedback, the enforcement of an all-or-nothing enterprise policy for the [`chrome.debugger` extension API](https://developer.chrome.com/docs/extensions/reference/api/debugger) can cause issues in certain environments. While we design a more flexible approach, we have decided to roll back this change. For details on how to apply the rollback, see our addendum to this [Chrome Developer blog post](https://developer.chrome.com/blog/debugger-enterprise-policy-restrictions#guidance_for_enterprise_administrators). ### Feature description (September 23, 2026) The [`chrome.debugger` extension API](https://developer.chrome.com/docs/extensions/reference/api/debugger) lets you send [Chrome DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/) commands to a specified `target`, for example, a tab, an iframe, or a service worker. When connecting (attaching) to a target, the API can now enforce permissions on managed browsers by validating enterprise host and screenshot policies. On enterprise devices, some policies can restrict extensions from attaching the debugger using an all-or-nothing model at attach time (`chrome.debugger.attach()`): - For hosts, the [ExtensionSettings](https://chromeenterprise.google/policies/#ExtensionSettings) enterprise policy can be configured to block hosts for an extension, returning the error `Host access is restricted by policy`. - For screenshots, the [DisableScreenshots](https://chromeenterprise.google/policies/#DisableScreenshots) enterprise policy disables screenshot capture or Data Loss Prevention (DLP) rules apply, returning the error `Screenshot capture is restricted by policy`. Developers can handle attach rejections gracefully or use higher-level APIs like [`chrome.scripting`](https://developer.chrome.com/docs/extensions/reference/api/scripting) and [`chrome.declarativeNetRequest`](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest) that support granular origin permissions in restricted enterprise environments. #
A TC39 proposal to add module `import … with { type: "text" }` statements to JavaScript. The import attribute loads text data as a string value. #
This feature was specified in this Spec.
Adds support for decoding JPEG XL (image/jxl) images in Blink using jxl-rs, a memory-safe pure Rust decoder (https://github.com/libjxl/jxl-rs). JPEG XL is a modern image format standardized as ISO/IEC 18181 that offers progressive decoding for improved perceived loading performance, support for wide color gamut, HDR, and high bit depth, and support for animation.
This feature was specified in this Spec.
The `margin-trim` CSS property may be used to omit margins before or after the first or last child of a container. This is supported on regular block containers and multicol containers. This is somewhat similar to the effect caused by the margin quirk that is applied to P, H1, H2... elements inside BODY and table cell elements (in quirks mode), but more powerful, generic, and expressive. Note: A previous version of the spec also applied this for flex and grid containers, but this has been removed. #
This feature was specified in this Spec.
Adds a "media-playback-while-not-visible" permission policy to allow embedders to pause audible media playback of embedded iframes which are currently hidden - i.e. "display" property set to "none"; "visibility" property set to "hidden"; or zero-area (width or height equal to 0). While hidden, attempts made by the embedded iframe to render audible media will be blocked. When the frame is shown again the prohibitions should be lifted. This should allow developers to build more user-friendly experiences and to also improve the performance by letting the browser handle the playback of content that is not visible to users. #
This feature was specified in this Spec.
Samples: https://gabrielsanbrito.github.io/media-playback-while-not-visible
Add srgb-linear and display-p3-linear color spaces (as defined by CSS) to PredefinedColorSpace for use with canvases. #
This feature was specified in this Spec.
We are expanding server side Gemini powered scam checks from just Android to desktop as well. This replaces the desktop on device model powered checks previously used.These checks are only for users enrolled in Enhanced Safe Browsing. Enterprises can control enrollment for their organization through the existing SafeBrowsingProtectionLevel policy. Chrome minimizes the amount of data shared with the server by only analyzing page text when a site exhibits high-confidence scam indicators. And whenever page content is sent off the device, it is processed ephemerally – meaning it is never logged, retained or used to train models.
This release of Chrome had 0 new origin trials.
This release of Chrome had 5 are available behind a flag.
Allows the use of 64-bit atomic minimum and maximum operations on `atomic<vec2u>` in WGSL. This provides WebGPU shader authors with a way to implement certain algorithms that use 64-bit atomics without requiring full support for 64-bit integers. #
This feature was specified in this Spec.
Adds the WebTransportOptions.datagramsReadableType constructor option. By default, incoming WebTransport Datagrams are exposed through a default ReadableStream . Applications that require BYOB reading can request a readable byte stream by setting datagramsReadableType: "bytes" . #
This feature was specified in this Spec.
Adds the modern WebTransport Datagram sending API. WebTransportDatagramDuplexStream.createWritable() creates independent WebTransportDatagramsWritable streams. Each writable has mutable sendGroup and sendOrder attributes for expressing relative priority among queued WebTransport data in the same send group. Chromium currently applies this ordering among Datagram writables. The implementation also reports the negotiated maximum outgoing Datagram payload size and discards oversized writes as required by the WebTransport specification. #
This feature was specified in this Spec.
Adds the standardized WebTransportReceiveStream interface, a ReadableStream subclass used for incoming unidirectional streams and the readable side of bidirectional streams. Its getStats() method returns per-stream byte counters: bytesReceived reports bytes received from the network, while bytesRead reports bytes delivered to the application. #
This feature was specified in this Spec.
Adds the WebTransport.reliability instance attribute and static WebTransport.supportsReliableOnly attribute. These APIs indicate whether the user agent supports WebTransport over exclusively reliable connections and whether an established session supports unreliable transport such as datagrams. In Chromium, reliability initially returns "pending" and changes to "supports-unreliable" after an HTTP/3 WebTransport connection is established. Since Chromium does not currently support HTTP/2 fallback, WebTransport.supportsReliableOnly returns false; any successfully established session uses HTTP/3 and supports unreliable datagrams. #
This feature was specified in this Spec.
To keep the platform healthy, we sometimes remove APIs from the Web Platform which have run their course. There can be many reasons why we would remove an API, such as:
Some of these changes will have an effect on a very small number of sites. To mitigate issues ahead of time, we try to give developers advanced notice so they can make the required changes to keep their sites running.
Chrome currently has a process for deprecations and removals of API's, essentially:
You can find a list of all deprecated features on chromestatus.com using the deprecated filter and removed features by applying the removed filter. We will also try to summarize some of the changes, reasoning, and migration paths in these posts.
This release of Chrome had 0 features deprecated.
This release of Chrome had 0 features removed.