Re: [csswg-drafts] [css-timing] reconsider name of frames() timing function

Thanks for the drawings @birtles !

I think using a `steps(3)` function to create four frames (or two frames) is _very_ confusing, especially if you're using it for flipping between actual animation still frames in a sprite sheet!  

Whatever the complaints about the start/end nomenclature, at least it's always clear that you get as many values as you specify, and that the time is divided into that many equal intervals.

I'm still in favor of `frames(n)` for n equal intervals, including both end points.   The n still has the same meaning from the perspective of dividing up the time into n intervals.  But the different name shows that we are counting/calculating the values differently.

Has there been any real demand for dropping both end points, or can that be deferred to a future spec?

-- 
GitHub Notification of comment by AmeliaBR
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1301#issuecomment-310591658 using your GitHub account

Received on Friday, 23 June 2017 07:19:14 UTC