- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Mon, 05 Jun 2023 20:56:31 +0000
- To: public-css-archive@w3.org
fantasai has just created a new issue for https://github.com/w3c/csswg-drafts: == [scroll-animations-1] blocking effects of timeline-scope == We added `timeline-scope` in #7759: ``` timeline-scope: none | <custom-ident> ``` Based on some clarifications from @flackr it seems the intention is not only to pull up the scope of a named descendant timeline, but also to block it from being further pulled up by a higher ancestor. (Also, due to error-handling, names declared that have zero or multiple possible descendant timeline bindings are treated as declaring an inactive timeline.) Put together, that gives a definition that looks like: > This property declares the scope of the specified timeline names to extend across this element’s subtree. > This allows a named timeline (such as a named scroll progress timeline or named view progress timeline) to be referenced by elements outside the timeline-defining element’s subtree—for example, by siblings, cousins, or ancestors. > It also blocks descendant timelines with the specified names from being referenced from outside this subtree, and ancestor timelines with the specified names from being referenced within this subtree. I'm opening this issue: 1. to confirm that we want to have this blocking behavior. 2. to ask if we want to add * a keyword to perform this blocking function on all possible timeline names (`contain`?) * a keyword to perform this blocking function all timeline names declared by this element (`local`?) Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8915 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 5 June 2023 20:56:32 UTC