nephele
/
haikuwebkit
1
0
Fork 0
Code Issues Releases Activity
haikuwebkit/LayoutTests/animations/multiple-animations-timing-...

6 lines
305 B
Plaintext
Raw Permalink Normal View History

2011-06-22 Young Han Lee <joybro@company100.net> Reviewed by Simon Fraser. animation-timing-function property with a list uses first item for all animations https://bugs.webkit.org/show_bug.cgi?id=60303 When an element has multiple animations that have different timingFunctions, the progress of each animation should be calculated using its respective timingFunction. But at this point, the timingFunction of the first animation is only used for the calculation, regardless of how many animations the element has. The code for getting a timingFunction is changed by this patch so that the timingFunction of the correct animation searched by its name will be used. * animations/multiple-animations-timing-function-expected.txt: Added. * animations/multiple-animations-timing-function.html: Added. 2011-06-22 Young Han Lee <joybro@company100.net> Reviewed by Simon Fraser. animation-timing-function property with a list uses first item for all animations https://bugs.webkit.org/show_bug.cgi?id=60303 When an element has multiple animations that have different timingFunctions, the progress of each animation should be calculated using its respective timingFunction. But at this point, the timingFunction of the first animation is only used for the calculation, regardless of how many animations the element has. The code for getting a timingFunction is changed by this patch so that the timingFunction of the correct animation searched by its name will be used. Test: animations/multiple-animations-timing-function.html * page/animation/KeyframeAnimation.cpp: (WebCore::getAnimationFromStyleByName): (WebCore::KeyframeAnimation::fetchIntervalEndpointsForProperty): Canonical link: https://commits.webkit.org/78773@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@89462 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2011-06-22 19:57:13 +00:00
PASS - "left" property for "box" element at 0.5s saw something close to: 18
PASS - "left" property for "box" element at 1.5s saw something close to: 124
PASS - "top" property for "box" element at 0.5s saw something close to: 75
PASS - "top" property for "box" element at 1.5s saw something close to: 181