WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
22919
Should use consistent algorithm to compute elapsedTime
https://bugs.webkit.org/show_bug.cgi?id=22919
Summary
Should use consistent algorithm to compute elapsedTime
Chris Marrin
Reported
2008-12-18 11:14:27 PST
KeyframeAnimation::animate() and AnimationBase::progress() both compute elapsedTime differently. This has not caused any visible problems so far. But with the new pauseAnimationAtTimeOnElementWithId() interface could expose problems since the differences are mostly in how they deal with pause. So I need to unify this into a common function
Attachments
Patch
(3.39 KB, patch)
2008-12-18 11:17 PST
,
Chris Marrin
mitz: review+
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Chris Marrin
Comment 1
2008-12-18 11:17:27 PST
Created
attachment 26125
[details]
Patch
Eric Seidel (no email)
Comment 2
2009-01-06 15:05:49 PST
Comment on
attachment 26125
[details]
Patch It appears the behavior or progress() for elapsed times < 0 changes with this patch. I don't have enough context to tell if that's a good thing or not.
Chris Marrin
Comment 3
2009-01-12 15:45:47 PST
It does change the elapsed time < 0 behavior. When reviewing this I noticed that difference. The current formula is a composite of the two old formulae and I believe the current one does the right thing in all cases.
Chris Marrin
Comment 4
2009-01-13 14:57:21 PST
Fixed by Changeset 39849
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug