Robert Flack

> The section on [custom effects](https://drafts.csswg.org/web-animations-2/#custom-effects) in the current level 2 spec starts with this issue: > > > This whole feature needs to be revisited. The current thinking is...

I think @bramus also had a good use case where an update callback would be much simpler ergonomically than needing to create a separate animation.

> And regarding using the target to play/pause: > > > I agree that conceptually it makes sense to not have a target, though it could be a nice feature...

> 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...

In the [starting of transitions](https://drafts.csswg.org/css-transitions/#starting), it says: > Likewise, define the after-change style as the computed values of all properties on the element based on the information known at the...

> I'm not exactly sure why the bug doesn't reproduce in Blink. Perhaps it is reflecting the changes to the style attribute as part of producing the before-change style? This...

> But these animations have already been canceled prior to any style change event. Temporarily un-canceling them seems like something different? I think of it as we haven't had a...

Seems like this relates to #6688 where I also brought up that this shouldn't trigger a transition - https://github.com/w3c/csswg-drafts/pull/6688#issuecomment-1505474485

> I wonder how often people will want to put interactive elements between options, I haven't seen a use case like that before. Maybe collapsible groups of options? Or a...

The [linked gpu gem](https://developer.nvidia.com/gpugems/GPUGems3/gpugems3_ch27.html) uses a trick for calculating motion blur where the previous camera position is used, however the proposal here is about the element's motion which isn't global...