- From: Bramus! via GitHub <sysbot+gh@w3.org>
- Date: Tue, 05 Sep 2023 20:01:02 +0000
- To: public-css-archive@w3.org
I’m very much sold on the idea.
Two remarks though:
1. For ScrollTimeline/ViewTimeline the range is not part of the Timeline; there are no `view-timeline-range` or `scroll-timeline-range` properties. Instead, the range part of the animation, using the `animation-range` property. That way one can re-use one timeline instance for multiple animations with different ranges.
I would suggest to do the same for container timelines.
1. ScrollTimeline and ViewTimeline also have anonymous timelines, via the [`scroll()`](https://drafts.csswg.org/scroll-animations/#scroll-notation) and [`view()`](https://drafts.csswg.org/scroll-animations/#view-notation) functional notations. Ideally there should also be an anonymous container timeline.
Strawperson proposal is to name it `container()`, with this syntax:
```
<container()> = container( <axis>? )
<axis> = block | inline | x | y
```
An anonymous container timeline would always look up the nearest container in the ancestor tree. The default value for `<axis>` is `block`.
--
GitHub Notification of comment by bramus
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6245#issuecomment-1707234285 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 5 September 2023 20:01:05 UTC