nephele
/
haikuwebkit
1
0
Fork 0
Code Issues Releases Activity
haikuwebkit/LayoutTests/animations/computed-style-expected.txt

25 lines
1.0 KiB
Plaintext
Raw Permalink Normal View History

2008-11-20 Simon Fraser <simon.fraser@apple.com> Reviewed by Darin Adler https://bugs.webkit.org/show_bug.cgi?id=20368 Implement getComputedStyle for animation properties. Remove individual computed values for transform-origin-x, transform-origin-y, and just return transform-origin instead. Return "none" for default animation-name, and fix the initial value. Tests: animations/computed-style.html transforms/computed-style-origin.html * css/CSSComputedStyleDeclaration.cpp: (WebCore::): (WebCore::getDelayValue): (WebCore::getDurationValue): (WebCore::getTimingFunctionValue): (WebCore::CSSComputedStyleDeclaration::getPropertyCSSValue): * rendering/style/RenderStyle.h: (WebCore::InheritedFlags::initialAnimationName): Canonical link: https://commits.webkit.org/30851@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@38642 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2008-11-21 00:26:29 +00:00
This tests computed style values from animation properties.
On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
PASS test1Style.webkitAnimationName is 'anim1'
PASS test2Style.webkitAnimationName is 'anim2, anim3'
2010-09-08 Dean Jackson <dino@apple.com> Reviewed by Simon Fraser. Implement steps() timing function for animations https://bugs.webkit.org/show_bug.cgi?id=44541 Tests: animations/timing-functions.html transitions/steps-timing-function.html * css/CSSComputedStyleDeclaration.cpp: (WebCore::getTimingFunctionValue): - when creating computed style we now test what type of timing function it being used * css/CSSParser.cpp: (WebCore::CSSParser::parseCubicBezierTimingFunctionValue): - rename this method from parseTimingFunctionValue (WebCore::CSSParser::parseAnimationTimingFunction): - support parsing the steps() function * css/CSSParser.h: - method rename * css/CSSStyleSelector.cpp: (WebCore::CSSStyleSelector::mapAnimationTimingFunction): - handle 'step-start' and 'step-end' identifiers. Also now use ::create when constructing objects * css/CSSTimingFunctionValue.cpp: (WebCore::CSSLinearTimingFunctionValue::cssText): (WebCore::CSSCubicBezierTimingFunctionValue::cssText): (WebCore::CSSStepsTimingFunctionValue::cssText): - new text output for computed style. We now produce the text 'linear' when appropriate. * css/CSSTimingFunctionValue.h: (WebCore::CSSTimingFunctionValue::isLinearTimingFunctionValue): (WebCore::CSSTimingFunctionValue::isCubicBezierTimingFunctionValue): (WebCore::CSSTimingFunctionValue::isStepsTimingFunctionValue): (WebCore::CSSTimingFunctionValue::CSSTimingFunctionValue): (WebCore::CSSTimingFunctionValue::isTimingFunctionValue): (WebCore::CSSLinearTimingFunctionValue::create): (WebCore::CSSLinearTimingFunctionValue::isLinearTimingFunctionValue): (WebCore::CSSLinearTimingFunctionValue::CSSLinearTimingFunctionValue): (WebCore::CSSCubicBezierTimingFunctionValue::create): (WebCore::CSSCubicBezierTimingFunctionValue::isCubicBezierTimingFunctionValue): (WebCore::CSSCubicBezierTimingFunctionValue::CSSCubicBezierTimingFunctionValue): (WebCore::CSSStepsTimingFunctionValue::create): (WebCore::CSSStepsTimingFunctionValue::numberOfSteps): (WebCore::CSSStepsTimingFunctionValue::stepAtStart): (WebCore::CSSStepsTimingFunctionValue::isStepsTimingFunctionValue): (WebCore::CSSStepsTimingFunctionValue::CSSStepsTimingFunctionValue): - CSSTimingFunction is now a pure virtual ref-counted base class, with subclasses for each of the three supported timing functions. * css/CSSValueKeywords.in: - new keywords step-start and step-end * page/animation/AnimationBase.cpp: (WebCore::solveStepsFunction): - produces the output value from a stepping function (WebCore::AnimationBase::progress): - now has to switch based on timing function type * page/animation/KeyframeAnimation.cpp: (WebCore::KeyframeAnimation::fetchIntervalEndpointsForProperty): - use ref-counted access * platform/animation/Animation.cpp: (WebCore::Animation::animationsMatch): - change timing function comparison for operator== * platform/animation/Animation.h: (WebCore::Animation::timingFunction): (WebCore::Animation::setTimingFunction): (WebCore::Animation::initialAnimationTimingFunction): - move to ref-counted timing function class * platform/animation/TimingFunction.h: (WebCore::TimingFunction::~TimingFunction): (WebCore::TimingFunction::isLinearTimingFunction): (WebCore::TimingFunction::isCubicBezierTimingFunction): (WebCore::TimingFunction::isStepsTimingFunction): (WebCore::TimingFunction::TimingFunction): (WebCore::LinearTimingFunction::create): (WebCore::LinearTimingFunction::~LinearTimingFunction): (WebCore::LinearTimingFunction::operator==): (WebCore::LinearTimingFunction::LinearTimingFunction): (WebCore::CubicBezierTimingFunction::create): (WebCore::CubicBezierTimingFunction::~CubicBezierTimingFunction): (WebCore::CubicBezierTimingFunction::operator==): (WebCore::CubicBezierTimingFunction::CubicBezierTimingFunction): (WebCore::StepsTimingFunction::create): (WebCore::StepsTimingFunction::~StepsTimingFunction): (WebCore::StepsTimingFunction::operator==): (WebCore::StepsTimingFunction::numberOfSteps): (WebCore::StepsTimingFunction::stepAtStart): (WebCore::StepsTimingFunction::StepsTimingFunction): - TimingFunction is now a ref-counted pure virtual base class, with three subclasses representing the types of timing functions that are supported. * platform/graphics/GraphicsLayer.h: (WebCore::AnimationValue::AnimationValue): (WebCore::FloatAnimationValue::FloatAnimationValue): (WebCore::TransformAnimationValue::TransformAnimationValue): - use PassRefPtr in function parameters * platform/graphics/qt/GraphicsLayerQt.cpp: (WebCore::solveStepsFunction): (WebCore::applyTimingFunction): (WebCore::AnimationQt::AnimationQt): (WebCore::AnimationQt::updateCurrentTime): - implement the timing function switch for QT * platform/graphics/mac/GraphicsLayerCA.mm: (WebCore::getCAMediaTimingFunction): - update for new timing function interface (WebCore::animationHasStepsTimingFunction): - new method to make sure animations with steps() functions never try to execute in Core Animation (WebCore::GraphicsLayerCA::addAnimation): - test for steps() timing function (WebCore::GraphicsLayerCA::timingFunctionForAnimationValue): * rendering/style/RenderStyleConstants.h: - remove old RenderStyle enum for timing function types Canonical link: https://commits.webkit.org/57777@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@67032 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2010-09-08 23:06:19 +00:00
PASS test3Style.webkitAnimationName is 'anim1, anim2, anim3'
2008-11-20 Simon Fraser <simon.fraser@apple.com> Reviewed by Darin Adler https://bugs.webkit.org/show_bug.cgi?id=20368 Implement getComputedStyle for animation properties. Remove individual computed values for transform-origin-x, transform-origin-y, and just return transform-origin instead. Return "none" for default animation-name, and fix the initial value. Tests: animations/computed-style.html transforms/computed-style-origin.html * css/CSSComputedStyleDeclaration.cpp: (WebCore::): (WebCore::getDelayValue): (WebCore::getDurationValue): (WebCore::getTimingFunctionValue): (WebCore::CSSComputedStyleDeclaration::getPropertyCSSValue): * rendering/style/RenderStyle.h: (WebCore::InheritedFlags::initialAnimationName): Canonical link: https://commits.webkit.org/30851@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@38642 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2008-11-21 00:26:29 +00:00
PASS test1Style.webkitAnimationDuration is '10s'
PASS test2Style.webkitAnimationDuration is '5s, 2.5s'
2010-03-05 Dean Jackson <dino@apple.com> Reviewed by Simon Fraser and Chris Marrin. Bug 26869: Add fill modes for CSS Animations https://bugs.webkit.org/show_bug.cgi?id=26869 Tests: animations/fill-mode-removed.html animations/fill-mode-transform.html animations/fill-mode.html * css/CSSComputedStyleDeclaration.cpp: * css/CSSParser.cpp: * css/CSSParser.h: * css/CSSPropertyNames.in: * css/CSSStyleSelector.cpp: * css/CSSStyleSelector.h: * css/CSSValueKeywords.in: - parse, assign and retrieve the value of the new -webkit-animation-fill-mode property * page/animation/AnimationBase.cpp: * page/animation/AnimationBase.h: - new state in animation engine for a finished animation that is "filling" forwards in time. This allows the engine to keep the animation around and not revert to the old style. - update the timer code to indicate it doesn't need to keep animating if it is filling - now that animations can extend beyond their elapsed time, make sure progress works correctly with iteration counts * page/animation/KeyframeAnimation.cpp: (WebCore::KeyframeAnimation::animate): - ensure correct style value is returned at the right time by checking for fill mode (WebCore::KeyframeAnimation::onAnimationEnd): - continue to send the end event, but only remove the animation if it isn't filling forwards * platform/animation/Animation.cpp: * platform/animation/Animation.h: - new fill mode member property * platform/animation/AnimationList.cpp: - ensure the fill mode is propagated to a list of style valus * platform/graphics/mac/GraphicsLayerCA.mm: - make hardware layers use Core Animation's fill mode Canonical link: https://commits.webkit.org/46873@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@55576 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2010-03-05 12:58:54 +00:00
PASS test1Style.webkitAnimationFillMode is 'backwards'
PASS test2Style.webkitAnimationFillMode is 'forwards, both'
2008-11-20 Simon Fraser <simon.fraser@apple.com> Reviewed by Darin Adler https://bugs.webkit.org/show_bug.cgi?id=20368 Implement getComputedStyle for animation properties. Remove individual computed values for transform-origin-x, transform-origin-y, and just return transform-origin instead. Return "none" for default animation-name, and fix the initial value. Tests: animations/computed-style.html transforms/computed-style-origin.html * css/CSSComputedStyleDeclaration.cpp: (WebCore::): (WebCore::getDelayValue): (WebCore::getDurationValue): (WebCore::getTimingFunctionValue): (WebCore::CSSComputedStyleDeclaration::getPropertyCSSValue): * rendering/style/RenderStyle.h: (WebCore::InheritedFlags::initialAnimationName): Canonical link: https://commits.webkit.org/30851@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@38642 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2008-11-21 00:26:29 +00:00
PASS test1Style.webkitAnimationIterationCount is '10'
PASS test2Style.webkitAnimationIterationCount is '10, infinite'
2010-09-08 Dean Jackson <dino@apple.com> Reviewed by Simon Fraser. Implement steps() timing function for animations https://bugs.webkit.org/show_bug.cgi?id=44541 Tests: animations/timing-functions.html transitions/steps-timing-function.html * css/CSSComputedStyleDeclaration.cpp: (WebCore::getTimingFunctionValue): - when creating computed style we now test what type of timing function it being used * css/CSSParser.cpp: (WebCore::CSSParser::parseCubicBezierTimingFunctionValue): - rename this method from parseTimingFunctionValue (WebCore::CSSParser::parseAnimationTimingFunction): - support parsing the steps() function * css/CSSParser.h: - method rename * css/CSSStyleSelector.cpp: (WebCore::CSSStyleSelector::mapAnimationTimingFunction): - handle 'step-start' and 'step-end' identifiers. Also now use ::create when constructing objects * css/CSSTimingFunctionValue.cpp: (WebCore::CSSLinearTimingFunctionValue::cssText): (WebCore::CSSCubicBezierTimingFunctionValue::cssText): (WebCore::CSSStepsTimingFunctionValue::cssText): - new text output for computed style. We now produce the text 'linear' when appropriate. * css/CSSTimingFunctionValue.h: (WebCore::CSSTimingFunctionValue::isLinearTimingFunctionValue): (WebCore::CSSTimingFunctionValue::isCubicBezierTimingFunctionValue): (WebCore::CSSTimingFunctionValue::isStepsTimingFunctionValue): (WebCore::CSSTimingFunctionValue::CSSTimingFunctionValue): (WebCore::CSSTimingFunctionValue::isTimingFunctionValue): (WebCore::CSSLinearTimingFunctionValue::create): (WebCore::CSSLinearTimingFunctionValue::isLinearTimingFunctionValue): (WebCore::CSSLinearTimingFunctionValue::CSSLinearTimingFunctionValue): (WebCore::CSSCubicBezierTimingFunctionValue::create): (WebCore::CSSCubicBezierTimingFunctionValue::isCubicBezierTimingFunctionValue): (WebCore::CSSCubicBezierTimingFunctionValue::CSSCubicBezierTimingFunctionValue): (WebCore::CSSStepsTimingFunctionValue::create): (WebCore::CSSStepsTimingFunctionValue::numberOfSteps): (WebCore::CSSStepsTimingFunctionValue::stepAtStart): (WebCore::CSSStepsTimingFunctionValue::isStepsTimingFunctionValue): (WebCore::CSSStepsTimingFunctionValue::CSSStepsTimingFunctionValue): - CSSTimingFunction is now a pure virtual ref-counted base class, with subclasses for each of the three supported timing functions. * css/CSSValueKeywords.in: - new keywords step-start and step-end * page/animation/AnimationBase.cpp: (WebCore::solveStepsFunction): - produces the output value from a stepping function (WebCore::AnimationBase::progress): - now has to switch based on timing function type * page/animation/KeyframeAnimation.cpp: (WebCore::KeyframeAnimation::fetchIntervalEndpointsForProperty): - use ref-counted access * platform/animation/Animation.cpp: (WebCore::Animation::animationsMatch): - change timing function comparison for operator== * platform/animation/Animation.h: (WebCore::Animation::timingFunction): (WebCore::Animation::setTimingFunction): (WebCore::Animation::initialAnimationTimingFunction): - move to ref-counted timing function class * platform/animation/TimingFunction.h: (WebCore::TimingFunction::~TimingFunction): (WebCore::TimingFunction::isLinearTimingFunction): (WebCore::TimingFunction::isCubicBezierTimingFunction): (WebCore::TimingFunction::isStepsTimingFunction): (WebCore::TimingFunction::TimingFunction): (WebCore::LinearTimingFunction::create): (WebCore::LinearTimingFunction::~LinearTimingFunction): (WebCore::LinearTimingFunction::operator==): (WebCore::LinearTimingFunction::LinearTimingFunction): (WebCore::CubicBezierTimingFunction::create): (WebCore::CubicBezierTimingFunction::~CubicBezierTimingFunction): (WebCore::CubicBezierTimingFunction::operator==): (WebCore::CubicBezierTimingFunction::CubicBezierTimingFunction): (WebCore::StepsTimingFunction::create): (WebCore::StepsTimingFunction::~StepsTimingFunction): (WebCore::StepsTimingFunction::operator==): (WebCore::StepsTimingFunction::numberOfSteps): (WebCore::StepsTimingFunction::stepAtStart): (WebCore::StepsTimingFunction::StepsTimingFunction): - TimingFunction is now a ref-counted pure virtual base class, with three subclasses representing the types of timing functions that are supported. * platform/graphics/GraphicsLayer.h: (WebCore::AnimationValue::AnimationValue): (WebCore::FloatAnimationValue::FloatAnimationValue): (WebCore::TransformAnimationValue::TransformAnimationValue): - use PassRefPtr in function parameters * platform/graphics/qt/GraphicsLayerQt.cpp: (WebCore::solveStepsFunction): (WebCore::applyTimingFunction): (WebCore::AnimationQt::AnimationQt): (WebCore::AnimationQt::updateCurrentTime): - implement the timing function switch for QT * platform/graphics/mac/GraphicsLayerCA.mm: (WebCore::getCAMediaTimingFunction): - update for new timing function interface (WebCore::animationHasStepsTimingFunction): - new method to make sure animations with steps() functions never try to execute in Core Animation (WebCore::GraphicsLayerCA::addAnimation): - test for steps() timing function (WebCore::GraphicsLayerCA::timingFunctionForAnimationValue): * rendering/style/RenderStyleConstants.h: - remove old RenderStyle enum for timing function types Canonical link: https://commits.webkit.org/57777@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@67032 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2010-09-08 23:06:19 +00:00
PASS test1Style.webkitAnimationTimingFunction is 'linear'
Querying transition-timing-function value on the computed style does not return keywords when it should. https://bugs.webkit.org/show_bug.cgi?id=105442 Reviewed by Simon Fraser. Source/WebCore: http://www.w3.org/TR/css3-transitions/#transition-timing-function-property contains a set of predefined timing functions which under the hood are implemented using cubic-bezier but it's an implementation detail that should not be exposed. It seems to be more clear to return a CSS keyword rather than the cubic-bezier form when querying the value of the property on the computed style. In fact the spec even say that for example the initial value is "ease" and not cubic-bezier(0.25, 0.1, 0.25, 1.0). We could also imagine that in the future these predefined values could contain other values not represented by a cubic-bezier form. This behavior also align with the "linear" keyword which return "linear" rather than cubic-bezier(0.0, 0.0, 1.0, 1.0). Test: transitions/transitions-parsing.html has been updated to cover the new behavior as well as making sure that an explicitly set value of cubic-bezier(0.25, 0.1, 0.25, 1.0) does not return "ease" but the cubic-bezier() form. * css/CSSComputedStyleDeclaration.cpp: (WebCore::createAnimationValue): (WebCore): (WebCore::getTimingFunctionValue): * css/CSSToStyleMap.cpp: (WebCore::CSSToStyleMap::mapAnimationTimingFunction): * platform/animation/TimingFunction.h: (WebCore::CubicBezierTimingFunction::create): (CubicBezierTimingFunction): (WebCore::CubicBezierTimingFunction::operator==): (WebCore::CubicBezierTimingFunction::timingFunctionPreset): Store the preset value of the timing function if it is one when creating it so we can use it later from the computed style. (WebCore::CubicBezierTimingFunction::CubicBezierTimingFunction): Source/WebKit2: Update the code to pass the animations from one process to another as the constructor of TimingFunction changed to take an extra parameter holding the type of the cubic-bezier form. * Shared/CoordinatedGraphics/CoordinatedGraphicsArgumentCoders.cpp: (CoreIPC::encodeTimingFunction): (CoreIPC::decodeTimingFunction): LayoutTests: Update the tests to match the correct behavior of returning a keyword rather than a cubic-bezier() form when using predefined values for the transition-timing-function property. * animations/animation-shorthand-name-order-expected.txt: * animations/animation-shorthand-name-order.html: * animations/animation-shorthand-removed.html: * animations/animation-shorthand.html: * animations/computed-style-expected.txt: * animations/computed-style.html: * fast/css/getComputedStyle/computed-style-expected.txt: * fast/css/getComputedStyle/computed-style-without-renderer-expected.txt: * svg/css/getComputedStyle-basic-expected.txt: * transitions/inherit-other-props-expected.txt: * transitions/inherit-other-props.html: * transitions/transitions-parsing-expected.txt: * transitions/transitions-parsing.html: Canonical link: https://commits.webkit.org/124207@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@138728 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2013-01-03 20:22:47 +00:00
PASS test2Style.webkitAnimationTimingFunction is 'linear, ease-in-out'
[CSS Easing 1] implement `jump-*` step positions https://bugs.webkit.org/show_bug.cgi?id=211271 Reviewed by Dean Jackson. LayoutTests/imported/w3c: * web-platform-tests/css/css-animations/parsing/animation-timing-function-computed-expected.txt: * web-platform-tests/css/css-animations/parsing/animation-timing-function-valid-expected.txt: * web-platform-tests/css/css-easing/step-timing-functions-output-expected.txt: * web-platform-tests/css/css-easing/step-timing-functions-syntax-expected.txt: * web-platform-tests/css/css-transitions/parsing/transition-timing-function-computed-expected.txt: * web-platform-tests/css/css-transitions/parsing/transition-timing-function-valid-expected.txt: * web-platform-tests/web-animations/timing-model/time-transformations/transformed-progress-expected.txt: Source/WebCore: Add support for `jump-start`, `jump-end`, `jump-none`, and `jump-both` step positions inside the `steps()` CSS timing function <https://drafts.csswg.org/css-easing-1/#step-position>. Adjust existing serialization logic to match the spec <https://drafts.csswg.org/css-easing-1/#serialization>: - omit `end` (and `jump-end`) - the value `step-start` should result in `steps(1, start)` instead of `step-start` - the value `step-end` should result in `steps(1)` instead of `step-end` Tests: animations/computed-style.html fast/css/animation-steps-calculated-value.html transitions/transitions-parsing.html web-platform-tests/css/css-animations/parsing/animation-timing-function-computed.html web-platform-tests/css/css-animations/parsing/animation-timing-function-valid.html web-platform-tests/css/css-easing/step-timing-functions-output.html web-platform-tests/css/css-easing/step-timing-functions-syntax.html web-platform-tests/css/css-transitions/parsing/transition-timing-function-computed.html web-platform-tests/css/css-transitions/parsing/transition-timing-function-valid.html web-platform-tests/web-animations/timing-model/time-transformations/transformed-progress.html * css/CSSValueKeywords.in: * css/parser/CSSPropertyParser.cpp: (WebCore::consumeSteps): (WebCore::consumeAnimationTimingFunction): * css/CSSComputedStyleDeclaration.cpp: (WebCore::createTimingFunctionValue): * css/CSSToStyleMap.cpp: (WebCore::CSSToStyleMap::mapAnimationTimingFunction): * css/CSSTimingFunctionValue.h: (WebCore::CSSStepsTimingFunctionValue::create): (WebCore::CSSStepsTimingFunctionValue::stepPosition const): Added. (WebCore::CSSStepsTimingFunctionValue::CSSStepsTimingFunctionValue): (WebCore::CSSStepsTimingFunctionValue::stepAtStart const): Deleted. * css/CSSTimingFunctionValue.cpp: (WebCore::CSSStepsTimingFunctionValue::customCSSText const): (WebCore::CSSStepsTimingFunctionValue::equals const): * platform/animation/TimingFunction.h: (WebCore::StepsTimingFunction::create): (WebCore::StepsTimingFunction::StepsTimingFunction): (WebCore::StepsTimingFunction::stepPosition): Added. (WebCore::StepsTimingFunction::setStepPosition): Added. (WebCore::StepsTimingFunction::clone): (WebCore::StepsTimingFunction::stepAtStart): Deleted. (WebCore::StepsTimingFunction::setStepAtStart): Deleted. * platform/animation/TimingFunction.cpp: (WebCore::operator<<): (WebCore::TimingFunction::transformTime): (WebCore::TimingFunction::createFromCSSValue): (WebCore::TimingFunction::cssText const): Source/WebInspectorUI: * UserInterface/Models/CSSKeywordCompletions.js: (WI.CSSKeywordCompletions.forFunction): Include the step position keywords when autocompleting the `steps()` CSS function. Source/WebKit: * Shared/WebCoreArgumentCoders.cpp: (IPC::ArgumentCoder<StepsTimingFunction>::encode): (IPC::ArgumentCoder<StepsTimingFunction>::decode): LayoutTests: * animations/computed-style.html: * animations/computed-style-expected.txt: * fast/css/animation-steps-calculated-value.html: * fast/css/animation-steps-calculated-value-expected.txt: * transitions/transitions-parsing.html: * transitions/transitions-parsing-expected.txt: Canonical link: https://commits.webkit.org/224221@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@261046 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2020-05-02 09:34:30 +00:00
PASS test3Style.webkitAnimationTimingFunction is 'steps(1, start), steps(1), steps(5)'
2008-11-20 Simon Fraser <simon.fraser@apple.com> Reviewed by Darin Adler https://bugs.webkit.org/show_bug.cgi?id=20368 Implement getComputedStyle for animation properties. Remove individual computed values for transform-origin-x, transform-origin-y, and just return transform-origin instead. Return "none" for default animation-name, and fix the initial value. Tests: animations/computed-style.html transforms/computed-style-origin.html * css/CSSComputedStyleDeclaration.cpp: (WebCore::): (WebCore::getDelayValue): (WebCore::getDurationValue): (WebCore::getTimingFunctionValue): (WebCore::CSSComputedStyleDeclaration::getPropertyCSSValue): * rendering/style/RenderStyle.h: (WebCore::InheritedFlags::initialAnimationName): Canonical link: https://commits.webkit.org/30851@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@38642 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2008-11-21 00:26:29 +00:00
PASS test1Style.webkitAnimationDirection is 'normal'
PASS test2Style.webkitAnimationDirection is 'normal, alternate'
PASS successfullyParsed is true
TEST COMPLETE