- From: Brian Birtles via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 Apr 2024 05:37:23 +0000
- To: public-css-archive@w3.org
> The intention of the hierarchy was mostly to simplify the spec, by having triggers follow animations as in: > For animations: ` timeline -> animation -> effect` > For triggers: `timeline -> trigger -> effect` > And since effects are attached to attachment ranges, have trigger follow the same mechanism. > > The idea was that they don't share anything, just follow the same structure, and the trigger simply affects the animation's playback according to its properties and state. Makes sense! > But, as @flackr mentioned, it's still too confusing and too complex, so I'll try and rewrite this without the effect part, and only with a trigger attached to a timeline and a range. Ok, I'll look forward to seeing what you come up with! -- GitHub Notification of comment by birtles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/10128#issuecomment-2060398295 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 17 April 2024 05:37:24 UTC