New in Chrome 152

Rachel Andrew

Published: August 25, 2026

Chrome 152 is rolling out now, and this post shares some of the key features from the release. Read the full Chrome 152 release notes.

Highlights from this release:

CSSPseudoElement support for ::backdrop, ::scroll-marker, and ::view-transition

Support for CSSPseudoElement in JavaScript, previously defined for ::after, ::before, and ::marker, extends to several new pseudo-elements in Chrome 152:

  • ::backdrop: Lets you handle interactions on modal dialog backdrops. For example, you can close a dialog when a user clicks the backdrop without interfering with clicks inside the dialog content, eliminating the need for complex intersection calculations.
  • ::scroll-marker: Enables interaction handling on scroll markers, such as collecting click statistics.
  • ::view-transition: Paves the way for geometry-aware view transitions and intercepting an active view transition mid-flight using coordinates of currently animating elements.

For more details on interacting with pseudo-elements in JavaScript, see the CSSPseudoElement documentation on MDN.

CPU Performance API

Chrome 152 introduces the CPU Performance API, which lets web applications determine the CPU performance of a user device.

Web applications can use this tier information to adapt the user experience to the device capabilities—such as scaling graphical fidelity, adjusting heavy computations, or tailoring background tasks. This API can also be used in combination with the Compute Pressure API, which provides real-time data about CPU pressure and utilization.

Users can override the reported performance tier in Chrome browser Settings > Performance > Speed > Override CPU performance tier. Administrators can also control this behavior using the CpuPerformanceTierOverride enterprise policy.

Connection Allowlists

Chrome 152 ships Connection Allowlists, a security mechanism that provides explicit control over external endpoints by restricting network connections initiated by a document or web worker.

Connection Allowlists provide a direct method to address these risks by making the browser the gatekeeper of all network connections originating from your page. By including the Connection-Allowlist HTTP response header, a site specifies the exact URL patterns permitted for all network communication initiated by its context.

To learn more about configuration and reporting options, read Connection Allowlists origin trial.

Further reading

This covers only some key highlights. Check the following links for additional changes in Chrome 152:

Subscribe

To stay up to date, subscribe to the Chrome Developers YouTube channel, and you'll get an email notification whenever we launch a new video. Or follow us on X or LinkedIn for new articles and blog posts.

As soon as Chrome 153 is released, we'll be right here to tell you what's new in Chrome!