- From: Yehonatan Daniv via GitHub <sysbot+gh@w3.org>
- Date: Sat, 24 Feb 2024 09:18:30 +0000
- To: public-css-archive@w3.org
> Why do we need to define the length of the group here? For groups in Web Animations 2, by default they calculate their length from their children. By "length" you mean duration? We don't need, I wasn't 100% sure whether the Group defines timing for its children or vice versa. So if it's defined by the children's duration then it's fine and we don't need to specify it again. So, IIUC, it's either we have "intrinsic" duration or "extrinsic" one. > I know that in the context if finite timelines we've also talked about allowing groups to behave like temporal flexbox containers where you'd set the group duration to 2s and let children specify their duration as a fraction of that. I can find the issues where we discussed that if that's helpful. That would certainly be great to have in future but I don't think that's the case in this example is it? That's super interesting on its own, but not necessary for this issue. > It looks like we're defining some basic timing properties that apply to each child in the group but I wonder if that's the right place to do it. Given that groups and children can have their duration defined separately, maybe the child timing properties should only be defined on the child. In your test-case you asked for a decaying stagger effect on the children: > The fade animations should slightly overlap and ideally the amount of overlap should steadily increase so that the start of "List item 2" and "List item 3" is nearly the same. So either we define specific `delay` on the children or `group-effect-align` on the parent. This is the syntax I proposed on #9561. It's like `place-items` and `place-self`, if you use `-align` on the parent you specify alignment for all the children in one property. If you specify `delay` you set that animation/group's alignment individually. -- GitHub Notification of comment by ydaniv Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9554#issuecomment-1962307854 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 24 February 2024 09:18:31 UTC