- From: Yehonatan Daniv via GitHub <sysbot+gh@w3.org>
- Date: Thu, 24 Oct 2024 22:16:40 +0000
- To: public-css-archive@w3.org
> With a custom effect callback, we could not do this sort of an optimization unless it was part of the API. Thanks for in-depth explanation! I get it now. But it seems that the only difference between the two is having a target, right? My main concern here is that creating a dummy `KeyframeEffect` with an empty object seems a bit awkward for an API. I suppose it would be better to also keep the `target` argument for `CustomEffect` as well. Then the UA could still optimize frames as you mentioned. > Most developers I've talked to don't manage all of the content on the site. Yes, I guess working on a large scale, generic tool forced us to take less chances and manage these more strictly. > And, having a rooted node to get the animations from for getAnimations Right! So adding the `target` argument should enable that too. -- GitHub Notification of comment by ydaniv Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6861#issuecomment-2436436518 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 24 October 2024 22:16:41 UTC