CSS

CSS corner shorthand properties Link copied!

Implements the CSS corner shorthand and per-corner sub-shorthands (corner-top-left, corner-top-right, corner-bottom-left, corner-bottom-right) as well as physical (corner-top, corner-bottom) and logical (corner-block-start, corner-block-end, etc.) edge shorthands. These allow setting both border-radius and corner-shape for individual corners in a single declaration. Additionally, corners is retained as a compat alias for the corner shorthand.

sampler: https://static.januschka.com/i-425897047/

CL: https://chromium-review.googlesource.com/c/chromium/src/+/7747994

Pending review

View Transitions: shadowRoots option in startViewTransition() Link copied!

Adds a shadowRoots sequence to StartViewTransitionOptions (defaulting to []). This allows document.startViewTransition() and element.startViewTransition() to discover participating elements (view-transition-name, view-transition-class, and view-transition-group) inside specified descendant ShadowRoots while preserving shadow DOM encapsulation.

JavaScript

Graphics

Pending review

Enhanced Canvas TextMetrics Link copied!

Expand the TextMetrics Canvas API to support selection rectangles, bounding box queries, and glyph cluster-based operations.

This new functionality should enable complex text editing applications with accurate selection, caret positioning, and hit testing. Additionally, cluster-based rendering facilitates sophisticated text effects such as independent character animations and styling.

DOM

Pending review

Capability Elements Icon-only mode Link copied!

Introduces a new attribute to render Capability Elements(<camera>, <microphone> and <geolocation>) as compact icon buttons without text using a displayhint attribute. This gives developers flexible UI density for spatial layouts such as map controls and video floating trays while preserving native security guarantees and full screen reader accessibility.

This is an extension to the recently released Capability Elements https://chromestatus.com/feature/5153829504024576

Pending review

SVG Path Data API Link copied!

Adds structured JavaScript access to SVG path data through three methods on SVGPathElement: getPathData() reads the path as an array of {type, values} objects containing each segment's command and numeric parameters. setPathData() updates the path from such an array, getPathSegmentAtLength() returns the segment at a specified distance along the path. These methods let developers inspect, edit, and construct paths without manually parsing or serializing the d attribute.

The optional getPathData({normalize: true}) setting simplifies path data to absolute move, line, cubic Bézier, and close commands (M, L, C, and Z). All three APIs operate on the base value of the d attribute, not CSS-computed or animated values.

Miscellaneous

Pending review

Prompt API Sampling Mode Link copied!

Allows developers to configure language model output variety and creativity in the Prompt API using high-level samplingMode presets. Instead of exposing raw numerical parameters like topK and temperature that vary unpredictably across models, developers can choose semantic presets ranging from "most-predictable" for deterministic extraction to "most-creative" for open-ended brainstorming. The browser maps these presets to optimal sampling hyperparameters for the underlying model, providing developers with reliable response tuning while preserving cross-browser interoperability.

enum LanguageModelSamplingMode { "most-predictable", // For strict consistency/factual extraction "predictable", // For highly focused outputs "slightly-predictable", // For moderately focused, consistent outputs "balanced", // The default state for standard prompting "slightly-creative", // For moderately varied, expressive outputs "creative", // For tasks favoring variety over strict facts "most-creative" // For maximum token diversity and brainstorming };

This feature is an enhancement of the Prompt API (https://chromestatus.com/feature/5134603979063296).

Web Bluetooth: BluetoothRemoteGATTServer.maxWriteWithoutResponseSize Link copied!

Adds BluetoothRemoteGATTServer.maxWriteWithoutResponseSize, which reports the largest payload that writeValueWithoutResponse() can send in one ATT packet. A maxwritewithoutresponsesizechanged event notifies applications when Chrome observes the value change, allowing applications to size chunks without assuming a 20-byte limit.

it depends on: https://chromestatus.com/feature/5138797158334464 and will be shipped together.

implementation: https://chromium-review.googlesource.com/c/chromium/src/+/7879985

Bug: 40265040, 40686244, 40163619

WebRTC

Multimedia

Shared MessagePort for AudioWorklet Link copied!

Exposes a shared MessagePort on AudioWorklet and AudioWorkletGlobalScope. This lets web applications communicate directly between the main thread AudioWorklet and the AudioWorkletGlobalScope without creating a bootstrap AudioWorkletProcessor only for message passing.

Network / Connectivity

Spec-compliant XML MIME type detection Link copied!

To fully align with Web standards, Chrome is updating how it detects XML MIME types. Chrome will now recognize valid MIME types whose subtype ends in +xml as XML across Chrome and Android WebView, including non-application types such as text/example+xml and image/example+xml.

For these responses, PerformanceResourceTiming.contentType returns application/xml. The value for image/svg+xml remains unchanged.

Enterprise web applications that rely on previous contentType values may observe behavior changes. Chrome Actor also uses this shared XML classification for dangerous MIME type navigation checks, so it may block navigations to additional non-application +xml responses. Admins should check whether their applications depend on these MIME types or the previous contentType values.

WebTransport connection statistics Link copied!

WebTransport.getStats() provides asynchronous statistics for an existing connection: round-trip time measurements when available, an estimated sending rate when available, and counts of expired, lost, and dropped datagrams. Statistics remain accessible after the connection closes. Chromium does not currently expose connection byte or packet totals.

Capabilities (Fugu)

Pending review

WebAppLaunch: user activation on focus-existing launch delivery Link copied!

Grants transient user activation to an installed web app's existing window when a launch is delivered into it through the launch_handler "focus-existing" client mode. Today the launchQueue consumer runs without activation even though the user clicked a link, shortcut, file, or share that caused the launch, so the page cannot call activation-gated APIs such as window.open() or requestFullscreen() in response. With activation granted at delivery, apps that use focus-existing to avoid duplicate windows can still open a separate window when the launched URL belongs to a different document or workspace, in the same way a click on a Notification created by the page already activates that page.

New origin trials

Opening links in a split tab Link copied!

Split screen scenarios are increasingly common. In addition to dual screen devices (i.e. physical split screen), many browsers have a split tab (i.e. virtual split screen) feature, where two tabs are tiled side-by-side within a single browser window. When using a split tab, there are multiple cases in which users want to open a link and view it side-by-side with the source page.

Today there is no way for a web author to request that a navigation open into a split tab. The existing navigation targets (_blank, _self, _parent, _top) cannot express this, and windowFeatures only offers popup, which opens a separate, detached browser window. Without popup, window.open() opens the content as a new full-size tab in the current window, which is the only other option available.

This feature provides methods (imperative and declarative) for web authors to request that a link open in a split tab, alongside the current page.

Deprecations and removals

Pending review

Deprecate and remove WebRTC peer connection method Link copied!

Starting in Chrome 160, Chrome will remove support for the RTCPeerConnection.createDTMFSender() method on Windows, macOS, Linux, ChromeOS, and Android.

This is a legacy, non-standard method that is obsolete and no longer conforms to the official Real-time communication for the web (WebRTC) standard. Removing it ensures better compatibility and security across different web browsers.

Before Chrome 160 is deployed, admins should test any internal or third-party web communication applications that rely on WebRTC. For more details on rollout dates, see the Chromium release schedule.