Chrome 152 stable ships the CPU Performance API, which gives the page a tier rating for the device's CPU. If your app scales graphical fidelity, runs heavy canvas or WebGL work, or trims background tasks, read the tier and adapt instead of sniffing the user agent or benchmarking at startup. It layers on Compute Pressure for real-time load, and users can override the reported tier in Settings.
The CSS side expands CSSPseudoElement to ::backdrop, ::scroll-marker, and ::view-transition. You can script a click on a dialog's backdrop without the old intersection-math dance, hook scroll markers, and grab a view transition partway through using the coordinates of the elements still animating.
Connection Allowlists is the security item: a Connection-Allowlist response header gates every network request a document or worker initiates behind an explicit allowlist of endpoints. If you run a security-sensitive app, that is a real lever against unexpected outbound calls. Two smaller wins round it out: the alpha() function from Color 5 sets just a relative color's alpha channel, so you stop spelling out a full color to tweak opacity, and app-region becomes window-drag for draggable title-bar areas in installed desktop PWAs.
None of these break anything, so the Monday call is triage: performance-tier work gets a standard API, view-transition-heavy UI gets scripting hooks, and the header allowlist is worth a read if third-party network calls keep biting you.