The big line in Chrome 152 isn't a feature, it's a removal: Manifest V2 extension support is now gone from stable, closing a migration Google has been dragging out for years. If you still maintain an MV2 extension, this is the release where it stops loading, and the only path forward is Manifest V3. It's also the last build on the four-week release train. From Chrome 153 in September the browser moves to a two-week cadence, so version numbers are about to start climbing twice as fast. On the platform side there's a genuinely useful batch for front-end work. New media-state pseudo-classes, `:playing`, `:paused`, `:seeking`, `:buffering`, `:muted` and the rest, let you style `<audio>` and `<video>` straight from their playback state with no JavaScript listeners. Relative alpha colors take an existing color and adjust only its transparency, and the new `window-drag` property marks regions of an installed web app that should behave like a titlebar. There's a security piece too: process isolation now leans on Windows ACLs to wall off Chrome's memory from other processes.