Preload by Agence Web Performance

Topic · 5 items

Firefox

This page gathers the Firefox updates Preload has covered: shipped features, measurement APIs, image formats and security decisions. A Firefox release is often what moves a feature to Baseline, making it usable everywhere. For each release, I look at what it unlocks for your sites and what needs checking.

Follow this topic By RSS, in your feed reader

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 ·

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 ·

: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

Preload #01 ·

deliveryType finally tells you when a resource came from cache

Firefox 158, out on October 13, supports PerformanceResourceTiming.deliveryType, which returns "cache" when a resource was served from the cache. Chrome and Edge have exposed it since version 117 and Safari since 26.4, so all four engines will have it, but its Baseline status has not been updated yet.

Not Baseline yet: Chrome 117, Safari 26.4, Firefox 158

Next step

In your field data, split cached resources from the rest before reading their timings, otherwise your averages mix two very different populations.

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.