- From: Yehonatan Daniv via GitHub <sysbot+gh@w3.org>
- Date: Tue, 16 Apr 2024 19:37:06 +0000
- To: public-css-archive@w3.org
@birtles thanks for reviewing! 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. 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. I've tried defining the constructs first in the initial draft. I'll move those into the Web Animations spec as suggested, and try to organize them together again in a simpler way. -- GitHub Notification of comment by ydaniv Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/10128#issuecomment-2059798310 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 16 April 2024 19:37:07 UTC