Re: [csswg-drafts] [scroll-animations-1] Bring back Scroll Offsets (#7575)

> To summarize, I think we've got the following proposals up for debate:
> 
> * Add  to `animation-delay` and `animation-duration`
> 
> * Length delays resolve to 0s when applied to time-based animations and vice versa. (Percentage components are maintained intact.)
> 
> * Length-based durations are ignored (treated as initial value) when applied to time-based animations, and vice versa.
> 
> * Offset values are not clamped within their declared range.
> 
> 
> @birtles Interested in your take on this discussion!

Thanks for including me and sorry for the delay (I was away last week and forgot to update my GitHub status).

I'm afraid I haven't been following the scroll animation discussion very closely so my input is probably not particularly valuable. Two very high-level notes, however:

1. An `Animation` is intended to be the vehicle that maps a static effect onto a timeline so extending the animation as in option 3 from the [original list of options](https://github.com/w3c/csswg-drafts/issues/7575#issuecomment-1207786782) would be the most natural fit from an architectural point of view.

    Because `animation-delay` maps onto an _effect_ it feels a little misaligned to me (i.e. the effect was supposed to be a "dumb", static, stateless thing agnostic of how it is used), but see the next point.

2. When we started out with scroll-linked animations, we were under the assumption that it would be desirable to dynamically switch between a time-based timeline and a scroll-based one (e.g. when the scroll passed some threshold, the author would use JS to swap out the timeline to a time-based one, letting the animation run to completion).

    Introducing different units to `animation-delay` and `animation-duration` such that some units are ignored depending on the type of timeline doesn't seem to be compatible with that assumption (or with the notion that effects are independent of how they are used), but maybe we've determined it's no longer an important use case?

-- 
GitHub Notification of comment by birtles
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7575#issuecomment-1320748822 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Saturday, 19 November 2022 02:05:46 UTC