Re: [csswg-drafts] [css-animations-2] Set `animation-trigger-type` as the coordinating list base property (#11653)

> animation-timeline can be specified in animation.

Right, just not implemented anywhere yet, but yes. So consider `animation-range` or `animation-easing` for that matter.

> Anyway, part of my confusion was that animation-trigger seems to be the first coordinating list property that cannot be specified in the same shorthand than the other properties of the same coordinating list property group.

And notice that `animation-range` is also a coordinating list property that cannot be specified in the same shorthand as its own group.
So I assume the list of `animation-trigger-*` properties should be coordinated the same way as `animation-range-*` properties do.

> The emphasized part of [this paragraph](https://drafts.csswg.org/css-animations-2/#animation-definition) should probably exclude animation-trigger

I think that paragraph is fine, since `animation-rage` and `animation-trigger` are in fact longhands of the `animation` shorthand, they're simply not specifiable inside it.

------------------

Regarding:

> The other part is that I thought that a coordinating list shorthand property should have its specified value serialized to empty string if the coordinating list base property has a different number of values than some property in the same group, indicating that it cannot represent all its longhands yet.
> 
> This is what FF does. Chrome truncates/repeats specified values as needed, which is incorrect because the spec requires this only for used values:
> 
> > The computed values of the coordinating list properties are not affected by such truncation or repetition.

I think this warrants a separate issue, to decide how to make this interoperable and whether this also warrants a spec change as well, or just close as "no change" and file issues for engine vendors.

-- 
GitHub Notification of comment by ydaniv
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/11653#issuecomment-2643456494 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 7 February 2025 16:48:18 UTC