Re: [csswg-drafts] [scroll-animations-1] naming the initial value of animation-range (#8406)

The CSS Working Group just discussed `[scroll-animations-1] naming the initial value of animation-range`, and agreed to the following:

* `RESOLVED: animation-range's initial value is the keyword "normal"`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> s/Topic/Subtopic<br>
&lt;TabAtkins> flackr: The default animation-range on SLA tells their relevant timeline<br>
&lt;TabAtkins> flackr: But these properties exist in general for time-based anims as well<br>
&lt;TabAtkins> flackr: for time-based, we're saying that the attachment point of the animation is what it would normally be<br>
&lt;TabAtkins> flackr: as discussed previously, basede on when the animation plays<br>
&lt;TabAtkins> flackr: So I'm suggesting the animation-range default should be 'auto', since there's a calc in play<br>
&lt;TabAtkins> flackr: Alternative is calling it normal<br>
&lt;TabAtkins> fantasai: for time-based, doesn't sound like it's that complicated? just 'start now', right?<br>
&lt;TabAtkins> flackr: Right, but we don't use 'normal' for anything yet<br>
&lt;TabAtkins> fantasai: We use normal in other props, like content:normal or line-height:normal, both of which aren't simple values either<br>
&lt;TabAtkins> florian: we tend to use normal for things taht *can* be complex but that are well-defined, while auto can be more magical<br>
&lt;TabAtkins> flackr: It's just bikeshedding, just wanted group opinion on whether auto or normal is better<br>
&lt;TabAtkins> fantasai: My take is that this is a normal thing to do, so "normal"<br>
&lt;TabAtkins> fantasai: while animation-range:auto kinda implies some more magical calculation based on other things maybe<br>
&lt;TabAtkins> flackr: I'm not opposed<br>
&lt;TabAtkins> astearns: other opinions?<br>
&lt;TabAtkins> astearns: Proposed resolution is that animation-range's initial value is "normal"<br>
&lt;TabAtkins> RESOLVED: animation-range's initial value is the keyword "normal"<br>
</details>


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


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

Received on Monday, 20 March 2023 15:20:53 UTC