Chrome switches to two-week releases from version 153 on desktop, Android and iOS

The source covers the release change in one sentence ^[1]. Its reading is that features and fixes will arrive more often, in smaller milestones ^[2]. The post does not give release dates or say how Chrome's testing channels line up under the new schedule. I think the cadence will reach more teams than any single panel change. Every team that ships to Chrome users has to test against new Chrome versions, whether or not it opens the new panels. On the new schedule, a three-version round-up like this one would cover about six weeks of releases ^[2].

Of the DevTools additions, the network replay is the best built. Resend repeats the request unchanged, with the same parameters, headers and body ^[3]. The post calls it the modern version of the old replay XHR, designed for a workflow now dominated by Fetch ^[7]. The edit variant is more useful. In the pre-filled Console command, the developer can change headers, body, query string or method, then press Enter to send it ^[6]. I like the Console as the place to edit. The modified request is plain code, so every change is visible in the command itself. The Copy menu still exports to curl, PowerShell, fetch and other formats ^[8].

The specificity tooltip is aimed at a habit the post names directly: adding !important just to make a rule win, when the real problem is often specificity ^[9]. It may retire some of those declarations, though not the ones already merged. For nested CSS, hovering a parent selector inside a nested rule now highlights the matching element on the page ^[11].

Preload work gets two small tools. A new Preloaded column in the Network panel shows whether a resource was loaded through preload ^[12]. Right-clicking a request and choosing Copy as preload element puts a ready-made link tag on the clipboard for the HTML ^[13]. For WebSocket and other binary payloads, the Payload tab has a built-in viewer that decodes to Base64, Hex or UTF-8 ^[14].

Soft-navigation timings have one condition. The Performance panel has to be open before the navigation. After the page change, the timings update and flag the navigation as soft ^[22]. The post defines a soft navigation as one where the URL and the perceived page change while JS and CSS stay loaded, as in a Next.js app ^[16].

For coding agents, the post also lists experiments with an alternative encoding, GCF, in place of JSON. The aim is to cut bandwidth when an agent has to analyse large amounts of data ^[18]. On a smaller scale, console.table output can now be copied as Markdown or CSV from its right-click menu ^[19].

The post's own summary is that these releases aim to shorten the time between seeing a problem and having a repeatable proof of it ^[20].