All posts
Motion

Scroll-Driven Animations Are Now Baseline, So Retire the Scroll Listener

web.dev: New to the web platform in October 2026

In August we argued that scroll-driven animations were worth shipping before they were Baseline. That caveat is gone. Firefox 159 turned them on by default, joining Chrome and Edge 115 and Safari 26, and web.dev now lists them as Baseline newly available.

The practical point for motion on websites: most scroll effects we used to build with a scroll listener or an intersection observer can now be plain CSS. A fade and lift as a card enters the viewport is a keyframe animation with animation-timeline set to view(). A reading progress bar is a scaleX animation on a scroll() timeline. Both run off the main thread, so they stay smooth on the cheap phones where JavaScript scroll handlers stutter.

Two rules we keep. Wrap every scroll animation in a prefers-reduced-motion check and give those users a static layout. And keep JavaScript for anything that has to change state, such as loading content or tracking analytics, because a CSS timeline animates, it does not run logic.

Then delete the old library. That is the real win.