Re: [csswg-drafts] [css-animations-2] Should the initial value for animation-duration be auto? (#6530)

The CSS Working Group just discussed `[css-animations-2] Should the initial value for animation-duration be auto?`, and agreed to the following:

* `RESOLVED: Add auto as default value`

<details><summary>The full IRC log of that discussion</summary>
&lt;Rossen_> https://github.com/w3c/csswg-drafts/issues/6530#issuecomment-1308954151<br>
&lt;dael> flackr: css animations spec the initial value to be 0sec but times don't make sense for scroll linked animations. In web default was auto<br>
&lt;dael> flackr: First is we should support auto in css animations because that's what we use to map to a range of scroll or view timeline<br>
&lt;bramus> +1<br>
&lt;heycam> q+<br>
&lt;dael> birtles: For background I think we added auto to web animations because we anticipated group effects where duration stretches to fill the group<br>
&lt;dael> heycam: What is the effect of specifying animation duration of some other value<br>
&lt;Rossen_> ack heycam<br>
&lt;dael> flackr: Currently have spec that if all durations are time based we convert to relative proportions of animation. This doesn't work for 0<br>
&lt;dael> flackr: And this is in web animations 2 spec<br>
&lt;dael> flackr: Not sure if we want to keep that or remove, but hope is most devs use auto which we convert to timeline specific<br>
&lt;dael> heycam: Yeah was just wondering if it's sensible to use specific time values. It's something authors will want to do and in that case is 0 sec useful. Sounds like no for 0<br>
&lt;ydaniv> q+<br>
&lt;dael> flackr: Right, 0 is not really something that should produce and effect<br>
&lt;dael> s/and/an<br>
&lt;Rossen_> ack ydaniv<br>
&lt;dael> ydaniv: Did you also consider allowing length and duration?<br>
&lt;dael> flackr: There is a separate issue filed for this.<br>
&lt;dael> ydaniv: but it's not colliding?<br>
&lt;dael> ydaniv: There's no collision between using auto as the initial<br>
&lt;dael> flackr: No, there should be no issue with using initial if we do length. Computed value of auto is 0 if they're not part of a group so we would just be saying computed value is whatever makes sense for a scroll linked animation<br>
&lt;dael> flackr: Proposal is that's 100%<br>
&lt;Rossen_> q?<br>
&lt;dael> Rossen_: Other opinions<br>
&lt;dael> flackr: Two proposals, one is add auto. auto as initial is separate proposal<br>
&lt;bramus> q+<br>
&lt;dael> flackr: I would like both<br>
&lt;Rossen_> ack bramus<br>
&lt;dael> bramus: I would like auto to be the default b/c if you set an animation timeline you need to change animation duration to 1sec or non-0 for animation timeline to work which is weird for author. for auto you don't need that<br>
&lt;dael> flackr: That's exactly why I want auto as initial<br>
&lt;dael> Rossen_: Prop: Add auto as default value<br>
&lt;dael> Rossen_: Obj?<br>
&lt;dael> RESOLVED: Add auto as default value<br>
</details>


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


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

Received on Thursday, 8 December 2022 00:21:25 UTC