nephele
/
haikuwebkit
1
0
Fork 0
Code Issues Releases Activity
haikuwebkit/LayoutTests/animations/missing-from-to-expected.txt

18 lines
1.5 KiB
Plaintext
Raw Permalink Normal View History

2010-06-25 Dean Jackson <dino@apple.com> Reviewed by Simon Fraser. https://bugs.webkit.org/show_bug.cgi?id=41188 Animations should not require 0% and 100% keyframes When we are generating the animation lists in CSSStyleSelector, rather than bail if we notice that "from" or "to" are missing, we now generate synthetic keyframes for those cases. Tests: animations/missing-from-to-transforms.html animations/missing-from-to.html WebCore/manual-tests/animation-with-transition.html * css/CSSStyleSelector.cpp: (WebCore::CSSStyleSelector::styleForKeyframe): Moved individual keyframe generation into a new function. (WebCore::CSSStyleSelector::keyframeStylesForAnimation): Call the new function above for regular keyframes, and also check for missing keyframes and generate them if necessary. * css/CSSStyleSelector.h: Canonical link: https://commits.webkit.org/52913@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@61933 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2010-06-26 02:01:29 +00:00
This test performs animations of the left property on five boxes over 2 seconds. Box 1 has all keyframes. Box 2 has a missing "from" keyframe. Box 3 has a missing "to" keyframe. Box 4 has both "from" and "to" keyframes missing, but other keyframes which should trigger the generation of "from" and "to". Box 5 has no keyframes, and should not animate. The test takes 3 snapshots each and expects each result to be within a specified range.
PASS - "left" property for "box1" element at 0.4s saw something close to: 20
PASS - "left" property for "box1" element at 1s saw something close to: 20
PASS - "left" property for "box1" element at 1.6s saw something close to: 15
PASS - "left" property for "box2" element at 0.4s saw something close to: 20
PASS - "left" property for "box2" element at 1s saw something close to: 20
PASS - "left" property for "box2" element at 1.6s saw something close to: 15
PASS - "left" property for "box3" element at 0.4s saw something close to: 20
PASS - "left" property for "box3" element at 1s saw something close to: 20
PASS - "left" property for "box3" element at 1.6s saw something close to: 15
PASS - "left" property for "box4" element at 0.4s saw something close to: 20
PASS - "left" property for "box4" element at 1s saw something close to: 25
PASS - "left" property for "box4" element at 1.6s saw something close to: 15
[Web Animations] Tests using the new animation engine may crash under WebCore::FrameView::didDestroyRenderTree when using internals methods https://bugs.webkit.org/show_bug.cgi?id=185612 <rdar://problem/39579344> Reviewed by Dean Jackson. Source/WebCore: Add a new internals.pseudoElement() method to obtain a pseudo element matching a given pseudo-id. This is necessary to be able to move off internals.pauseTransitionAtTimeOnPseudoElement() and internals.pauseAnimationAtTimeOnPseudoElement() for Web Animations testing. * testing/Internals.cpp: (WebCore::Internals::pseudoElement): * testing/Internals.h: * testing/Internals.idl: LayoutTests: Some tests that were opting into the new animation engine were using internals methods (pauseAnimationAtTimeOnElement, pauseTransitionAtTimeOnElement, etc.) that enforce the creation of animations in the old animation engine. Meanwhile, the code that toggles the animation engine used based on HTML comments is run prior to teardown of the previous test and so a test running with the new engine would run with the legacy engine during teardown. These two factors would cause `ASSERT(!frame().animation().hasAnimations())` to fail under FrameView::didDestroyRenderTree(). We update tests that use these internals method to use the Web Animations API instead and opt into the new animation engine if they didn't already do that. * animations/animation-hit-test-transform.html: * animations/keyframes-dynamic-expected.txt: * animations/keyframes-dynamic.html: * animations/missing-from-to-expected.txt: * animations/missing-from-to-transforms-expected.txt: * animations/missing-from-to-transforms.html: * animations/missing-from-to.html: * fast/css-generated-content/pseudo-animation.html: * transitions/transition-hit-test-transform.html: Canonical link: https://commits.webkit.org/201087@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@231766 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2018-05-14 18:19:30 +00:00
PASS - "left" property for "box5" element at 0.4s saw something close to: 10
PASS - "left" property for "box5" element at 1s saw something close to: 10
PASS - "left" property for "box5" element at 1.6s saw something close to: 10
2010-06-25 Dean Jackson <dino@apple.com> Reviewed by Simon Fraser. https://bugs.webkit.org/show_bug.cgi?id=41188 Animations should not require 0% and 100% keyframes When we are generating the animation lists in CSSStyleSelector, rather than bail if we notice that "from" or "to" are missing, we now generate synthetic keyframes for those cases. Tests: animations/missing-from-to-transforms.html animations/missing-from-to.html WebCore/manual-tests/animation-with-transition.html * css/CSSStyleSelector.cpp: (WebCore::CSSStyleSelector::styleForKeyframe): Moved individual keyframe generation into a new function. (WebCore::CSSStyleSelector::keyframeStylesForAnimation): Call the new function above for regular keyframes, and also check for missing keyframes and generate them if necessary. * css/CSSStyleSelector.h: Canonical link: https://commits.webkit.org/52913@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@61933 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2010-06-26 02:01:29 +00:00