- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Tue, 27 May 2025 14:05:38 +0000
- To: public-css-archive@w3.org
> allow a flag to be passed in to the pause procedure (at a spec level, not the API level) that allows overriding the endpoint behavior whilst paused. Yup, this sounds good and matches my thinking as well, to add at a spec level a start point exclusive paused state. > (Could scroll animations use something like this too?) Scroll animations are endpoint inclusive in a running state, however, if we make this endpoint state modification apply while running as well then we could use this. > we can scrap Animation.trigger and just have AnimationTrigger.arm(Animation) In this sort of a model I would just call it add/remove. This could either be AnimationTrigger.add/removeAnimation (similar to Element.add/removeEventListener) or AnimationTrigger.animations.add/remove (similar to Element.classList. We should also consider whether we really need to have multiple animations per trigger. If instead we had an animation attribute on the trigger we could say that setting it to a different animation disassociates the trigger from the original animation and might simplify some of the state management. If developers want to use the same trigger for multiple animations there just needs to be an easy way to construct a trigger with the same options as an existing trigger. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12119#issuecomment-2912647102 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 27 May 2025 14:05:39 UTC