[css-animations-2] Should animation triggers be their own spec?

[fantasai]

Currently we have folded all of the animation triggers features into Animations Level 2. With Scroll Animations, we put the key integration points into Animations Level 2, but pulled the bulk of it into its own module. Should we do the same with Animation Triggers?

And regardless, shouldn't we publish a Working Draft of this huge new feature and invite wide review?

[ydaniv]

@fantasai:

And regardless, shouldn't we publish a Working Draft of this huge new feature and invite wide review?

Currently all the spec text in web-animations-2 is obsolete since we did an overhaul of this feature to introduce Event Triggers, granular actions, and multiple timelines per trigger.

@tabatkins did a rewrite of the high-level author-facing spec text in css-animations-2 + the declarative syntax to reflect better these changes.

So no need for publishing and review until we finish rewriting the entire feature to reflect latest resolutions.

With Scroll Animations, we put the key integration points into Animations Level 2, but pulled the bulk of it into its own module. Should we do the same with Animation Triggers?

In the case of Animation Triggers we split the spec into 2:

1. High-level, author-facing part with declarative syntax in css-animations-2.
2. Lower-level, implementor-facing part with imperative syntax in web-animations-2.

We could extract all of it into a separate, single module for animation-triggers. That sounds like a good idea.
Only thing that might be a problem, I don't know if bikeshed can handle cyclic dependencies. Since this module will definitely import names from css-animations and web-animations 1 & 2, but we may need to import names back into web-animations-2 for the imperative interfaces. Unless we can somehow define these as delta extensions to these interfaces in that new module?

cc @tabatkins @flackr

[ydaniv]

If we do decide to split this into a separate module, then I suppose it would be animation-triggers-1.
And as for editors, so far I believe we had contributions from: @DavMila, @flackr, @szager-chromium, @tabatkins, and myself (@ydaniv). Also with offline contributions from @bramus and @fantasai.

[fantasai]

Bikeshed has no problems with specs referencing each other back and forth. We do it all the time.

[css-meeting-bot]

The CSS Working Group just discussed [css-animations-2] Should animation triggers be their own spec?, and agreed to the following:

• RESOLVED: create animation-triggers-1 module
• RESOLVED: editors will be flackr, DavidA and ydaniv

The full IRC log of that discussion

<JoshT> ydaniv: raised by fantasai. animation trigger is spread out on css-animations-2 and web-animations-2
<JoshT> ... one the implementation syntax. one author facing
<flackr> q+
<JoshT> ... it might make sense to grab all of it and have it in its own module
<JoshT> ... but concerned we might have problems with cyclic imports. is it an issue with bikeshed tool?
<JoshT> ... if not, I support the proposal
<bramus> +1
<astearns> ack flackr
<JoshT> ... have animation-triggers-1, assign editors
<JoshT> flackr: first thing is the way we define animation triggers, they could be used in other specs in the future. are they more generic triggers?
<JoshT> ... second, all of the trigger specific stuff about when to activate and deactivate belongs in the spec, but should keep the animation-trigger and the web animation trigger property in those specs
<JoshT> ... all of the details about how to set up a trigger move to a new spec
<bradk> I have to leave
<bradk> Bye
<JoshT> astearns: opinions on whether it's aimation-triggers or triggers?
<bradk> 😀
<JoshT> flackr: could we rename the shorthand later?
<bramus> css-triggers?
<JoshT> fantasai: yes ChrisL can do it
<JoshT> astearns: proposal is to create a css animation triggers spec and move everything into it
<JoshT> bramus: could we call it css-triggers and encapsulate all types of triggers
<JoshT> flackr: could it apply to things other than animations in the future
<JoshT> fantasai: from a branding perspective, I think animation triggers for now. people looking for it would look for that
<JoshT> RESOLVED: create animation-triggers-1 module
<JoshT> RESOLVED: editors will be flackr, DavidA and ydaniv
<JoshT> ydaniv: what shortname. have css- prefix?
<JoshT> astearns: without css- for now