Preload by Agence Web Performance

Topic · 4 items

Safari

This page collects what Safari and WebKit change for your sites: features that finally work everywhere, Safari-specific behavior and pitfalls you only see on an iPhone. Preload follows stable releases here, along with the betas worth checking before they ship.

Follow this topic By RSS, in your feed reader

Preload #04 ·

Safari: one failed modulepreload can break a page until the next tab

A Safari visitor can stay stuck on a page after a single transient error (a 404, a CDN incident, a dropped request): in WebKit, a <link rel="modulepreload"> that fails stays recorded as loaded, and a later import() of the same URL rejects without retrying the request, even once the file is back. WebKit fixed it in Safari Technology Preview 255, released October 22; Safari 27.2, shipped October 26, doesn't mention the fix. Sites split into preloaded JavaScript modules, as many build tools produce, are exposed.

Next step

Test the failure path: make a module fail to load once, restore it, then check that a new request goes out. Add a bounded retry on the same URL (no random query parameter, which would create a separate module), and make sure your CDN and service worker don't keep serving the failed response.

In our October 28 test, the rejection survived a tab reload in Playwright's WebKit 27.2, while Chrome 156 and Firefox 157 retried the request: only a new tab unblocked the page.

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 ·

Safari 27 blocks services that track visitors by their email address

Your attribution and audience numbers may shift without you shipping anything: in iOS, iPadOS, macOS and visionOS 27, Safari cuts network access to third-party “identity resolution” infrastructure, WebKit announced on October 19. These services grab the email address typed at sign-in or sign-up and turn it into an opaque tracking identifier, so they can follow the person across sites and devices. The block works at the domain level, so reshaping the request won't get around it, and WebKit doesn't name any service.

Next step

If attribution, audience matching or third-party requests drop, compare Safari with other browsers first, before blaming the site or its performance. In a third-party audit, count what Safari blocks separately.

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

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.