You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In trying to analyze the specced behavior for updating the finished state when the timeline is inactive I came up with the following two scenarios.
Scenario A:
Suppose we have a finished animation and its timeline becomes inactive
--> we will have a resolved hold time
Then suppose we lengthen the duration such that the animation shouldn't be finished anymore
--> we should keep the hold time in that case
Then suppose the timeline becomes active again
--> we should keep the start time and pick up where we left off
Seems OK.
Scenario B:
Suppose we have a finished animation and its timeline becomes inactive
--> we will have a resolved hold time
Then suppose we seek to within the active interval such that the animation shouldn't be finished animation
--> we will update the hold time and clear the start time (the procedure to silently set the current time will do this)
Then suppose the timeline becomes active again
--> we should recalculate the start time from the hold time but there's nothing in the spec that does that yet
This is a bug. Step 2 puts us into the paused state which seems wrong.
From @birtles on May 20, 2015 8:23
In trying to analyze the specced behavior for updating the finished state when the timeline is inactive I came up with the following two scenarios.
Scenario A:
--> we will have a resolved hold time
--> we should keep the hold time in that case
--> we should keep the start time and pick up where we left off
Seems OK.
Scenario B:
--> we will have a resolved hold time
--> we will update the hold time and clear the start time (the procedure to silently set the current time will do this)
--> we should recalculate the start time from the hold time but there's nothing in the spec that does that yet
This is a bug. Step 2 puts us into the paused state which seems wrong.
Copied from original issue: w3c/web-animations#95
The text was updated successfully, but these errors were encountered: