- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Sep 2021 14:56:34 +0000
- To: public-css-archive@w3.org
> JS-first stance, and then translated to CSS I support this rethink (I never liked `selector()` either), but if the CSS approach can't be expressed in terms of reasonable primitives shared with the JS API, this is going to be hard to both spec and implement. BTW, what happens if we access `Animation.timeline` on a CSS-created scroll-linked animation? Will we create new interfaces separate from the current `ScrollTimeline` interface? (E.g. `ViewTimeline`). > view timelines global to the page > might be difficult to implement On the one hand, this is Weird and New (boo!). On the other hand, the mode of operation for scroll-linked animations is to base the timeline state on layout information from the previous frame. Assuming we're sticking with that, global/broad names seem possible. -- GitHub Notification of comment by andruud Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6674#issuecomment-930256709 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 29 September 2021 14:56:36 UTC