- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Sep 2021 16:09:02 +0000
- To: public-css-archive@w3.org
I like this idea, and have a few notes from previous conversation with Scott. I think most relevant: - The most common use-case is that each property has a start-value and end-value aligned to particular container sizes, and an easing curve to interpolate. It’s rare (but not impossible) for a single property to have additional/intermediate “stops” defined. In that way, it can be thought of more like a transition than a keyframe animation. - However, it is useful to define multiple related properties in the same place, even if they have different start/end points. A keyframe animation with multiple stops makes that possible in [Typetura](https://docs.typetura.com/). I could imagine an approach similar to `@scroll-timeline`, or a way to use media/container breakpoint values directly in the keyframes rule (or some variant of it), though I haven't started digging into the details of either approach. Unlike scroll-timeline, I don't think it works for the "source" element to be hard-coded (unless it is the viewport). For a container-relative approach, authors should be able to describe the animation/timeline once, and have it respond to individual container contexts. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6581#issuecomment-916238083 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 9 September 2021 16:09:03 UTC