- From: Antoine Quint via GitHub <sysbot+gh@w3.org>
- Date: Tue, 04 Jun 2024 07:32:41 +0000
- To: public-css-archive@w3.org
> The `CustomEffect` idea lacks too much. The idea with KeyframeEffect is you get easing curves between key frames, which is very nice. > > If I understand correctly, with `CustomEffect`, we're entirely on our own, we have to implement key frames and easing in JavaScript. The idea of `CustomEffect` is that you get _all_ of the timing and animation features provided by the Web Animations API for free while using a callback-based approach to applying animation values. So, easing, delay, duration, iterations, playback rate, etc. will be accounted for to produce the `progress` value provided to the callback. Keyframes however are a feature of `KeyframeEffect` so would indeed not be available there. > What we need is the same APIs, but for simply applying to numbers on JS objects instead of style properties on elements. That's the only difference there should be. That's a fair point, I think you should contribute to [the `CustomEffect` issue](https://github.com/w3c/csswg-drafts/issues/6861). -- GitHub Notification of comment by graouts Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9974#issuecomment-2146814655 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 4 June 2024 07:32:42 UTC