- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Fri, 25 Oct 2024 19:08:54 +0000
- To: public-css-archive@w3.org
> But it seems that the only difference between the two is having a target, right? And that if you want to simultaneously animate some css properties you'd generally end up creating multiple animations. My thinking was that by having a hook on regular animations you could run script driven animations in tandem with the css property update rather than having to set the two up separately. I imagine developers may often animate a custom property which drives the logic of the custom effect. > Right! So adding the target argument should enable that too. Yeah, the optimization part might end up being a bit non-trivial to implement, e.g. the UA wouldn't necessarily know whether the developer would animate the position of the element, however, we should spec it to be able to skip calling the the animation update function in cases like `content-visibility: hidden` or where the UA thinks the target element won't be visible (e.g. clipped or otherwise contained). -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6861#issuecomment-2438615520 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 25 October 2024 19:08:54 UTC