On 2014/11/05 16:25, Brian Birtles wrote:
Yes, this is clearly wrong. It came about because we've changed the
behaviour regarding if/when start time becomes unresolved a few times.
When the pause completes we should set the hold time to the result of
calculating the current time using the original start time. As the issue
notes, it might actually make more sense to keep the start time until
the pause completes which would make calculating this easier.
I'll update the spec to do that.
Fixed:
https://github.com/w3c/web-animations/commit/c2ee69787c8cd6ecff7d5b90d499b0f58afc56aa
