Ashutosh Biswas's Frontend Masters article on scrubbable staggered animations uses a combination of newer CSS features and a formula he himself calls "a huge formula and can look intimidating." The goal is a generic mechanism that can map a progress value — scroll progress or any other input — onto a staggered animation. That generality carries real complexity, and for the common case of staggering elements as they scroll into view, much of it is unnecessary.

A scroll-driven scenario is one Ashutosh presents as an ideal use of the formula. But the spec for scroll-driven animations already accounts for dropping time in favor of scroll progress, and animation-delay has no effect on scroll-driven animations because it is only meaningful on the default time-based document timeline. That gap is what animation-range-start fills: it delays a scroll-driven animation relative to scroll progress rather than time.

Replacing the formula with one declaration

The demo under discussion is a donation tally in the site footer whose digits animate in one after another as the reader scrolls — a subtle scrollytelling touch. One observation about the effect: if a user scrolls quickly, the per-digit entrances can pass too fast to notice, which makes the tally a reasonable case study for scroll-driven versus scroll-triggered animations. That comparison is a separate topic; here the point is only how much the staggering itself can be simplified.

Where the original leans on custom CSS functions and a large derivation, a single line of CSS covers the same stagger, relying on sibling-index() to increment animation-range-start per sibling:

animation-range-start: contain calc(10% + 2.5% * sibling-index());

The 2.5% step comes from having eight characters to stagger, with the delays spread at even intervals so the final character enters at 30% of the containment range (10% + 20%). The fork preserves the original functionality, so the stagger is only visible when scrolling gradually.

What the single-timeline approach gives up

Consolidating everything into one animation has a cost that is easy to miss. Ashutosh notes in the original that easing keywords, cubic-bezier() and linear() cannot be used and that easing functions must be built by hand. That follows from the design: once all staggered animations are merged into one master timeline, animation-timing-function applies to the whole timeline rather than to each element. There is no CSS defect here — just the consequence of a "single predictable, holistic effect driven by one progress value." The animation-timing-function property behaves the same for scroll-driven animations as for time-based ones; for example, steps() can drive scroll-linked sprite animation.

So the custom-function route is not without value: merging everything into one timeline is exactly what you would want when the sub-animations must stay interrelated and the whole effect is driven by an input the browser does not natively support. It is also true that plugin replaced browser features have often earned their place when they offer control otherwise unavailable, and scroll timelines themselves replace JavaScript techniques developers had used for decades. The question is whether the donation tally needs that power. It appears not to, which makes the original implementation overbuilt for its example.

Far-out uses of progress as an input

What remains compelling in the original is its reach beyond scroll: linking animation progress to an arbitrary input value, much like scroll timelines do. Custom animation timelines would make that possible, and interesting inputs are not hard to think of — text fields that advance an animation as they are filled in, an indicator of how closely a typed password matches a required pattern, progress through a quiz or a shopping cart, or a karaoke display in which a ball bounces along text highlighting it in step with a user's sung progress measured by speech recognition. Until such timelines exist, a custom-function approach like Ashutosh's is likely the closest available route to driving CSS animations from values other than time or scroll progress.