Preload by Agence Web Performance

Topic · 8 items

Chrome

This page gathers the Chrome updates Preload has covered: shipped features, removals, DevTools and CrUX field data. It is for front-end and web developers who need to know what the most widely used browser changes for their sites. For each release, I look at what becomes usable everywhere and what needs fixing.

Follow this topic By RSS, in your feed reader

Preload #04 ·

Sitemaps and RSS feeds will show as plain text in Chrome from November 17

The change mainly hits the styling of XML sitemaps and RSS or Atom feeds dressed up with an XSL stylesheet: starting with Chrome 158, due in stable on November 17, Chrome no longer runs XSLT, so these files will display in the browser as raw XML, in plain text. They keep working normally for search engine crawlers and feed readers. The removal also affects code calling XSLTProcessor; only sites enrolled in an origin trial and machines managed with the XSLTEnabled enterprise policy keep XSLT, until Chrome 176 (August 2027).

Next step

For a sitemap or a feed, the simplest option is to leave it as is: plain-text display has no impact on crawlers. If you really want a human-readable version, serve HTML to browsers and XML to crawlers, which amounts to cloaking and takes more work to set up and maintain: your call, it isn't essential. If your site uses XSLT elsewhere (XSLTProcessor, transformed XML pages), move the transformation to the server.

Google puts XSLT usage at 0.02% of page loads. For most sites, the only visible effect will be how SEO plugin sitemaps look, and only humans open those in a browser.

Read the source

Preload #03 ·

CSS scroll-driven animations become Baseline with Firefox 159

From October 27, you can tie a CSS animation to scrolling in every major browser, without JavaScript: Firefox 159 turns on scroll-driven animations by default, already available in Chrome 115 and Safari 26. The animation-timeline property, with the scroll() function (a container's scroll progress) and the view() function (an element's position in the visible area), plus the animation-range property, cover reveal-on-scroll, reading progress bars and parallax, which used to rely on AOS, GSAP ScrollTrigger or hand-written scroll listeners.

Baseline, newly available: Chrome 115, Safari 26, Firefox 159

Next step

Find the scroll effects still driven by JavaScript and rewrite them with animation-timeline, animating only transform and opacity, which stay off the main thread. Turn them off under prefers-reduced-motion and keep them as a progressive enhancement, for instance inside an @supports (animation-timeline: view()) block, so older browsers show the content without the effect.

This is a good time to drop a JavaScript library that ships on many brochure sites, and get a smoother effect that frees up the main thread.

Read the source

Preload #03 ·

Chrome measures the weight of ads, with two blind spots

Ads often slow down the pages that show them, without anyone knowing exactly which ones. Chrome can now recognize them (using EasyList, a public ad filter list, and the script that loads them), and DevTools, the browser's built-in diagnostic tool, shows them in an Ads tab: processing time and download size per ad, and a list of ad scripts. Google also publishes four metrics measured on real visitors (screen space taken, count, processing, size) for sites that declare their ad sellers in their ads.txt file.

Next step

On a page with ads, open DevTools (F12 key), Application panel, Ads tab: you'll see which ads and scripts weigh the most. Then cross-check with the Performance panel to find which ones make the page slow to respond to clicks.

Two blind spots in our tests: an ad script running directly in the page isn't counted, only ad frames are, and a Chrome driven by a testing tool shows everything at 0. The script list is therefore more reliable than the total for knowing which ad network slows the site down.

Read the source

Preload #03 ·

An AI agent can now analyze an application's memory leaks

For a single-page application (SPA) whose memory keeps growing during a session, chrome-devtools-mcp 1.12.0, the MCP server that gives an AI agent access to Chrome DevTools, can analyze a heap snapshot (a snapshot of the JavaScript memory heap) without a connected browser since October 22, with paginated results. The release also runs independent tool calls in parallel, hot-reloads its configuration with --watchConfig and masks WebSocket headers in its logs. On the DevTools side, the Memory panel now flags unused closure variables kept alive by a shared V8 context, sorted by memory impact.

Next step

Take a heap snapshot in the Memory panel, have your agent analyze it through this server, then check its findings with the Objects retained by contexts filter.

Read the source

Preload #03 ·

Certificate authority keys exposed: Chrome and Firefox drop eMudhra

A valid TLS certificate could be forged for any domain: on October 17, the private keys of eight intermediate certificates from the Indian authority eMudhra, six of them for TLS, turned out to be recoverable (flawed generation, keys too small). Chrome blocked them that evening through CRLSet and announced it will remove the affected eMudhra root, Firefox revoked them through OneCRL, and Mozilla is urgently removing emSign ECC Root CA G3. eMudhra estimates around 30,000 certificates need to be migrated.

Next step

Update the certificate stores on your servers, Docker images and runtimes (Node.js did so on October 21), then redeploy. If one of your sites uses an emSign certificate, switch authorities, and never turn off TLS verification to work around an error.

Read the source

Preload #02 ·

Chrome no longer runs unload handlers at all

What Edge shipped last week is now done in Chrome too: since version 155, unload handlers no longer run on any page load, wrapping up a gradual rollout that began in March 2025. Only the unload Permissions-Policy and an enterprise policy remain as escape hatches, and Chromium is about to make this the default for every browser built on it. Google says unload usage dropped from 18% to under 4% of navigations, and about 5% more navigations are now eligible for the back/forward cache.

Next step

Hunt down any remaining unload listeners, third-party scripts included, and move them to pagehide or visibilitychange. Remove any Permissions-Policy: unload=(self) header, which brings the listener back and excludes the page from the cache again. Firefox still drops pages that listen for unload, so the cleanup pays off there too.

Read the source

Preload #02 ·

:buffering, :playing, :paused: Chrome plans media pseudo-classes for version 158

Safari since 15.4 and Firefox since 150 let you style a <video> or <audio> element by its state: :playing, :paused, :seeking, :buffering, :stalled, :muted and :volume-locked. Chrome has published its intent to ship them and targets version 158, due in stable on November 17, with Edge to follow. If the schedule holds, the group will then become Baseline.

Partial support: Safari 15.4, Firefox 150, Chrome 158 planned

Next step

Show a video player's loading indicator with video:buffering instead of JavaScript waiting and playing listeners, and keep the script as a fallback for Chrome until 158.

Less JavaScript for a state the browser already knows. You can ship this as a progressive enhancement today, without waiting for Chrome.

Read the source

Preload #01 ·

JPEG XL arrives in Chrome 155, then in Firefox 158

Chrome 155, stable since October 6, decodes JPEG XL images with a new decoder written in Rust. Firefox 158 enables it by default on October 13 and adds image/jxl to the Accept header of its image requests. Safari has decoded it since version 17, for still images only. Google recommends trying both AVIF and JPEG XL and keeping whichever performs better: JPEG XL shines mostly for high-fidelity and lossless photos.

Partial support: Chrome 155, Firefox 158, Safari 17 without animation or progressive decoding

Next step

Compare JPEG XL and AVIF on your high-fidelity photos, then serve JPEG XL inside <picture> with a <source type="image/jxl"> placed before the AVIF and WebP sources, never on its own.

One more format in <picture>, not a switch. AVIF stays the first choice until your own measurements say otherwise.

Read the source

Eroan Boyer
Founder of Agence Web Performance

What comes next, Tuesday morning.

Items on this topic land in Preload every week, two weeks before they go public. Free, one-click unsubscribe.