- From: Brian Birtles via GitHub <sysbot+gh@w3.org>
- Date: Thu, 12 Apr 2018 09:34:27 +0000
- To: public-css-archive@w3.org
> 10:41 AM birtles: Are values other than 'auto' valid for the iteration duration value? If not, should step 3 of https://drafts.csswg.org/web-animations-1/#update-the-timing-properties-of-an-animation-effect specify also that we should check whether the value is 'auto' and bail if it's not? > 10:42 AM I'm also not clear from the spec when 'auto' should be parsed, I assume it's implicit in the "duration → iteration duration" step since most of the spec treats 'iteration duration' as a number > 10:43 AM Oh wait, but getTiming() has to return 'auto' so I guess it has to live > 6:29 PM smcgruer: Yeah, that could definitely be more clear. I think it might come down to this sentence, "In this level of this specification, the string value auto is equivalent to zero." But "equivalent" is way too under-specified. > 6:29 PM Yeah, 'auto' needs to be preserved. > 6:30 PM This is actually more clear in level 2 which has the "intrinsic iteration duration" concept. > 6:30 PM Something got lost when I split the levels out. > 6:31 PM It has, "The string value auto is used to indicate that the iteration duration reflects the animation effect’s intrinsic iteration duration." > 6:31 PM And then it has various definitions for the intrinsic iteration duration. > 6:31 PM Do you mind filing an issue? I'm pretty sure the birtles/smcgruer in that log have been switched. -- GitHub Notification of comment by birtles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2471#issuecomment-380740500 using your GitHub account
Received on Thursday, 12 April 2018 09:34:31 UTC