- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Mon, 27 Feb 2023 17:02:11 +0000
- To: public-css-archive@w3.org
> Incidentally, if we made the timeline the point where the frame rate was controlled I think we would avoid a lot of these issues. I agree, I think the timeline is the right place for the framerate control. It also implies all animations on the same timeline would be aligned to the same ticks (which is presumably what you would want in most cases), and answers a bunch of other questions. > It's more clumsy, since you'd need to create a new `DocumentTimeline` instance (and the mapping to CSS might get a bit more awkward too) but at least the API would always be consistent and easy to understand. I think we could make the mapping to CSS work. E.g. this would probably be specifying a different `animation-timeline` set up to be a different rate. Maybe using an `@timeline` rule to set up a different global named timeline which ticks at a different rate. I also think it would be nice if you could modify the default document timeline to tick at a different rate if you want to as a site set the rate of your animations by default. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7196#issuecomment-1446699633 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 27 February 2023 17:02:13 UTC