Re: [web-animations] computedTiming.iterationStart and fill attributes

The computed timing should return the values used for timing calculations.
We should clarify this in the specification.

Cheers,
    -Shane

On Mon Dec 15 2014 at 6:05:13 PM "Сергей Грехов" <sgrekhov@unipro.ru> wrote:

> Hi All,
>
> It's unclear from the spec what values should return
> computedTiming.iterationStart and fill attributes for some values.
> Example:
>
>     var timing = {
>         iterationStart: -100,
>         duration: 1000
>     };
>     var animation = new Animation(target, [], timing);
>     var player = document.timeline.play(animation);
>
>     animation.computedTiming.iterationStart == ? // -100 or 0?
>     animation.computedTiming.fill == ? // 'auto' or 'none'?
>
> Specification only reads that these attributes of computed timing return
> fill mode and iteration start properties of animation node. For timing
> calculations
> (http://w3c.github.io/web-animations/#dom-animationtiming-iterationstart)
> "Values less than zero are clamped to zero for the purpose of timing model
> calculations." and
> (http://w3c.github.io/web-animations/#dom-animationtimingreadonly-fill)
> "When performing timing calculations the special value auto is expanded to
> one of the fill modes recognized by the timing model..."
>
> But what shoul be returned by computedTiming? Original value or the one
> that used for timing calculations?
>
> --
> Sergey G. Grekhov
>
>
>
>