kevers-google

view-timeline-range: cover | contain | start | end | [ custom offset pair ] sounds good. I share Brian's concern over potential confusion if we overload 'phase" with a different...

I also quite like: > ``` > view-timeline-range: [start|end]? [start|end]? ? > ``` This would even allow reversing the direction of the animation by reversing the edges. progress = (position...

Expanding on Rob's idea: In the web-animations-1 spec, timeline.currentTime is a scalar quantity and used in animation.currentTime calculations. It is possible that we could extend the notion of current time...

Gotcha. So an animation would run between X% and Y% where the percentages are calculated based on the named range? We already have the start and end delays for an...

Leaning towards option 1 as it seems easier for the web developer (less verbose than option 2 and avoids potential confusion due to over-specification with option 3).

The chrome implementation does not actually call the web-animations-2 procedure for setting the timeline when the timeline is updated via a style change rather than an API call (it probably...

The animation API has a cancel method. In your example, the "if" and "else" blocks look the same. Should the blocks be setting different keyframe options? If so, then rather...

Yes, animation.cancel() puts the animation into an idle state where it is no longer active. The animation will eventually be garbage collected provided there are no live references in JavaScript....

Should we add a link to the collection in the README.