- From: Matt Perry via GitHub <sysbot+gh@w3.org>
- Date: Fri, 11 Aug 2023 14:23:59 +0000
- To: public-css-archive@w3.org
I can see the argument for opting all animations on the page to a lower rate but I think it would be incomplete without a way of excepting some animations/JS callback loops (`CustomEffect`/`rAF`) that want to run in sync with higher fps paints or input, like scroll or touch. In terms of the proposed names, it would make more sense to be able to define a `targetFramerate` directly, with values higher than the display simply capped at the display framerate. We never want to scale framerates for perceptual reasons and this more direct setting would make it obvious what's happening here. Or, given that there will be a handful of framerates that people will commonly want to define, also allow some names with explicit, unambiguous mapping: - `film`: `24` - `low`: `30` - `high`: `60` - `fluid`: `120`/`144` -- GitHub Notification of comment by mattgperry Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7196#issuecomment-1674878348 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 11 August 2023 14:24:00 UTC