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

This is almost certainly a dumb question, but why are all these special cases needed? Why can't the correct behaviour be deduced in the animation logic?

For example:

- if the final and initial states of the animation would look the same to the user; 
- if the animation is going to repeat;
-  if the user asks for `frames(N)`; 
- then divide into N+1 frames and display the first N for that run of the loop.

Do something similar looking at the final state (accounting for fill) on the the last run.

And automatically drop the first frame, on the first run, if it it resembles the state before the animation started.

Make `frames()` do the right thing out the box. If necessary, `steps()` can be extended for those rare cases when the right thing is wrong.

GitHub Notification of comment by fuchsia
Please view or discuss this issue at using your GitHub account

Received on Friday, 7 July 2017 10:16:45 UTC