Re: [csswg-drafts] [scroll-animations-1] Add a way for timeline-scope to pull up all contained timelines (#9158)

The CSS Working Group just discussed `[scroll-animations-1] Add a way for timeline-scope to pull up all contained timelines`, and agreed to the following:

* `RESOLVED: Add 'all' keyword to 'timeline-scope', equivalent to specifying all possible names`

<details><summary>The full IRC log of that discussion</summary>
&lt;YehonatanDaniv> bramus: this issue is about declaring many animation timelines and using broader scope<br>
&lt;YehonatanDaniv> ... this issue is about using "all" for hoisting them up<br>
&lt;flackr> q+<br>
&lt;YehonatanDaniv> ... allow also anchor name for hoisting up using anchor scope<br>
&lt;Rossen_> ack flackr<br>
&lt;YehonatanDaniv> flackr: can a timeline be pooled up with multiple scope<br>
&lt;YehonatanDaniv> fantasai: no<br>
&lt;fantasai> s/pooled/pulled/<br>
&lt;bramus> s/pooled/pulled/<br>
&lt;fantasai> scribenick: fantasai<br>
&lt;fantasai> fantasai: the 'all' keyword traps all the keywords, just like individual keywords trap those keywords<br>
&lt;fantasai> ... might be useful if you want to encapsulate<br>
&lt;fantasai> flackr: ok<br>
&lt;fantasai> Rossen_: any other concerns?<br>
&lt;fantasai> bramus: proposed to add "all" which will pull up all timelines<br>
&lt;fantasai> (It's basically the same as specifying all possible names)<br>
&lt;schenney> The concern raised by flackr is already in the issue, raised by https://github.com/w3c/csswg-drafts/issues/9158#issuecomment-1742797028<br>
&lt;fantasai> YehonatanDaniv: if I name something in a descendant, and then specify all in an ancestor, what happens?<br>
&lt;fantasai> flackr: the lower scope captures that name, it won't be pulled higher up<br>
&lt;fantasai> RESOLVED: Add 'all' keyword to 'timeline-scope', equivalent to specifying all possible names<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9158#issuecomment-1854241301 using your GitHub account


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

Received on Wednesday, 13 December 2023 16:16:08 UTC