Chrome Release Summary
+153
Chrome 160
Enabled (17) | Origin Trial (1) | Behind a flag (0) | Deprecated (1) | Removed (0)Enabled by default in 160
This release of Chrome had 17 new features.
CSS corner shorthand properties
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 #
This feature was specified in this Spec.
CSSPseudoElement.selectorText
CSSPseudoElement is a javascript api that allows some limited interactions with pseudo elements from script. This feature adds a minor improvement, namely selectorText property, that returns the string that could be used to select this pseudo element from CSS. #
This feature was specified in this Spec.
Canvas2D tone mapping
Adds a toneMapping option to CanvasRenderingContext2DSettings, allowing a 2D canvas context to specify 'standard' or 'extended' tone mapping behavior when displaying HDR content, unifying the tone mapping API across 2D canvas and WebGPU. #
This feature was specified in this Spec.
Capability Elements Icon-only mode
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 #
This feature was specified in this Spec.
Case-sensitive anchor name matching in quirks mode
Anchor name matching for fragment navigation will become case-sensitive in quirks mode, matching the behavior in standards mode. Previously, navigating to #Foo could match <a name="foo"> in quirks mode. This aligns Chromium with Safari, Firefox, and the HTML specification, which do not perform case-insensitive matching. #
This feature was specified in this Spec.
Enhanced Canvas TextMetrics
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. #
This feature was specified in this Spec.
Prompt API Sampling Mode
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). #
This feature was specified in this Spec.
Resources
No linked docsSamples: https://isaacahouma.github.io/prompt-api-sampling-presets
RTP Header Extension Encryption
Allows using SRTP encryption to cover RTP header extensions and contributing source (CSRC) identifiers. #
This feature was specified in this Spec.
Regular Expression Buffer Boundaries
A TC39 proposal introducing `\A`, `\z` and `\Z` character escapes to Unicode-mode regular expressions as synonyms for `(?-m:^)`, `(?-m:$)` and `(?=(?:\r\n|\n|\r|\u2028|\u2029)?(?-m:$))`, respectively. #
This feature was specified in this Spec.
SVG Path Data API
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. #
This feature was specified in this Spec.
Resources
Docs: https://docs.google.com/document/d/1uCVUqYGKgsCCu7LEtEdO3Yuea-MT-I2XsU6Eoe3mlQI/edit?usp=sharing
No linked samplesShared MessagePort for AudioWorklet
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. #
This feature was specified in this Spec.
Resources
Docs: https://developer.mozilla.org/docs/Web/API/AudioWorkletGlobalScope/port
No linked samplesSharedWorkerConnectEventEmptyStringData
The data attribute of the SharedWorker connect event is now initialized to the empty string, instead of null, as per the HTML spec. #
This feature was specified in this Spec.
Spec-compliant XML MIME type detection
To fully align with Web standards, Chrome is updating how it detects [XML MIME](https://www.rfc-editor.org/info/rfc7303/) 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. #
This feature was specified in this Spec.
View Transitions: shadowRoots option in startViewTransition()
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 `ShadowRoot`s while preserving shadow DOM encapsulation. #
This feature was specified in this Spec.
Web Bluetooth: BluetoothRemoteGATTServer.maxWriteWithoutResponseSize
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 #
This feature was specified in this Spec.
Resources
No linked docsSamples: https://static.januschka.com/i-40265040
WebAppLaunch: user activation on focus-existing launch delivery
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. #
This feature was specified in this Spec.
WebTransport connection statistics
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. #
This feature was specified in this Spec.
Resources
Docs: https://developer.mozilla.org/en-US/docs/Web/API/WebTransport/getStatshttps://w3c.github.io/webtransport/#web-transport-connection-stats
Samples: https://github.com/MicrosoftEdge/Demos/tree/main/webtransport-getstatshttps://microsoftedge.github.io/Demos/webtransport-getstats
Origin Trials in-progress in 160
This release of Chrome had 1 new origin trials.
Opening links in a split tab
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. #
Resources
No linked docsSamples: https://mfreed7.github.io/split-tabs/test/demo.html
Flagged features in 160
This release of Chrome had 0 are available behind a flag.
Deprecations and Removals
Deprecation policy
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:
- They are superseded by newer APIs.
- They are updated to reflect changes to specifications to bring alignment and consistency with other browsers.
- They are early experiments that never came to fruition in other browsers and thus can increase the burden of support for web developers.
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:
- Announce on the blink-dev mailing list.
- Set warnings and give time scales in the Chrome DevTools Console when usage is detected on the page.
- Wait, monitor, and then remove the feature as usage drops.
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.
Deprecated features in 160
This release of Chrome had 1 features deprecated.
Deprecate and remove WebRTC peer connection method
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](https://webrtc.org/)) 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](https://chromiumdash.appspot.com/schedule). #
This feature was specified in this Spec.
Removed features in 160
This release of Chrome had 0 features removed.