Re: [csswg-drafts] [scroll-animations] Broader scope of scroll timelines (#7759)

> Detaching these two operations onto multiple elements is advanced stuff. We should make it comprehensible also, but it shouldn't be interfering with making the common case as simple and straightforward as possible.

Yeah, that's fine. My listing of shorthand possibilities was just obeying the usual maxim of "defaults match the longhand initial values", but as you're well aware that doesn't have to be the case. ^_^ I think it's completely reasonable for `scroll-timeline: foo` to be equivalent to `scroll-timeline-name: foo; scroll-timeline-axis: block;`, and requiring `scroll-timeline: foo none;` to get the "just create, don't attach" behavior.

We could alternately fix this by adding an "auto" timeline-axis keyword and use *that* as the initial value, so then omitting it from the shorthand would do the right thing with the usual behavior.

--------

> I think each named timeline could still implicitly serve as a local root for that name as well as the selected timeline for the ancestor declared name if one existed. This would allow descendants to continue to be valid and use the same timeline in their happy subtree bubble.

Apologies @flackr, could you elaborate on this? I'm not completely sure what behavior you're suggesting here.

I *think* you're saying that if you, say, write `scroll-timeline: foo block;`, this will automatically attach to an ancestor establishing a `foo` timeline (but not attaching an axis) if one exists, and create its own `foo` timeline if there's one (and attach the axis). And you can force the "create a timeline" behavior regardless of ancestors by setting `-scope: foo`?


-- 
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7759#issuecomment-1522370188 using your GitHub account


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

Received on Tuesday, 25 April 2023 20:25:01 UTC