CSS Scroll-Driven Animations Aren't Baseline Yet, Ship Them Anyway

CSS scroll-driven animations, the animation-timeline scroll family of properties, now sit at around 82.6% global browser support according to caniuse, just short of the usual 85% Baseline threshold because Firefox stable still keeps the feature behind a flag, even though it's already on by default in Nightly and marked as an Interop 2026 priority.

That missing few percent shouldn't stop you using it today. The spec was designed as a progressive enhancement from the start: you author the finished state of an element as the default, then layer the scroll driven animation on top only where it's supported. Browsers that don't understand animation-timeline simply ignore that line and show the plain, finished version. Nobody sees a broken half animated mess, they just don't get the scroll effect yet.

That's a genuinely different risk profile to most wait for Baseline situations, where an unsupported feature actively breaks something. Here, the fallback is invisible and free. If a project would benefit from a scroll triggered reveal or parallax effect, it's worth building it in CSS now rather than waiting on Firefox to catch up, or reaching for a JavaScript library to do a job the platform is about to do natively for everyone anyway.