Add perf tests for animations using different CSS value types

Add perf tests for animations using different CSS value types

This adds perf tests for CSS and Web Animations over the following
CSS value types:
 - Color
 - Filter
 - Length
 - Length 3D
 - Shadow
 - Transform

BUG=309981
Committed: https://crrev.com/0f604440fa0d538d402a4213152ee6a48fd97ad1
Cr-Commit-Position: refs/heads/master@{#316677}

[alancutter (OOO until 2018), 2015-02-17 02:00:24]

alancutter@chromium.org changed reviewers:
+ qyearsley@chromium.org, shans@chromium.org

[sullivan, 2015-02-17 14:30:30]

sullivan@chromium.org changed reviewers:
+ sullivan@chromium.org
- qyearsley@chromium.org

[sullivan, 2015-02-17 14:30:31]

lgtm

https://codereview.chromium.org/931723002/diff/20001/tools/perf/page_sets/tou...
File tools/perf/page_sets/tough_animation_cases/resources/css_value_type.js
(right):

https://codereview.chromium.org/931723002/diff/20001/tools/perf/page_sets/tou...
tools/perf/page_sets/tough_animation_cases/resources/css_value_type.js:14:
console.assert(document.getElementById('container'));
Are these left in intentionally because they make it easier to debug when
something goes wrong?

[qyearsley, 2015-02-17 17:51:39]

qyearsley@chromium.org changed reviewers:
+ qyearsley@chromium.org

[qyearsley, 2015-02-17 17:51:40]

https://codereview.chromium.org/931723002/diff/20001/tools/perf/page_sets/tou...
File tools/perf/page_sets/tough_animation_cases/resources/perftesthelper.js
(right):

https://codereview.chromium.org/931723002/diff/20001/tools/perf/page_sets/tou...
tools/perf/page_sets/tough_animation_cases/resources/perftesthelper.js:4:
(function(){
[Optional] You could also make this file match the style guide. The body of a
function is normally indented 2 spaces, including for function expressions.

http://www.chromium.org/developers/web-development-style-guide
https://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml

[alancutter (OOO until 2018), 2015-02-17 20:42:12]

Thanks for the reviews.

https://codereview.chromium.org/931723002/diff/20001/tools/perf/page_sets/tou...
File tools/perf/page_sets/tough_animation_cases/resources/css_value_type.js
(right):

https://codereview.chromium.org/931723002/diff/20001/tools/perf/page_sets/tou...
tools/perf/page_sets/tough_animation_cases/resources/css_value_type.js:14:
console.assert(document.getElementById('container'));
On 2015/02/17 14:30:31, sullivan wrote:
> Are these left in intentionally because they make it easier to debug when
> something goes wrong?

Yes. There are a couple of preconditions to this script and I think asserts are
the simplest way to document and enforce them.

https://codereview.chromium.org/931723002/diff/20001/tools/perf/page_sets/tou...
File tools/perf/page_sets/tough_animation_cases/resources/perftesthelper.js
(right):

https://codereview.chromium.org/931723002/diff/20001/tools/perf/page_sets/tou...
tools/perf/page_sets/tough_animation_cases/resources/perftesthelper.js:4:
(function(){
On 2015/02/17 17:51:40, qyearsley wrote:
> [Optional] You could also make this file match the style guide. The body of a
> function is normally indented 2 spaces, including for function expressions.
> 
> http://www.chromium.org/developers/web-development-style-guide
> https://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml

Will do in separate patch.

[alancutter (OOO until 2018), 2015-02-17 20:42:17]

The CQ bit was checked by alancutter@chromium.org

[commit-bot: I haz the power, 2015-02-17 20:43:25]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/931723002/20001

[commit-bot: I haz the power, 2015-02-17 22:35:07]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-02-17 22:35:55]

Patchset 2 (id:??) landed as
https://crrev.com/0f604440fa0d538d402a4213152ee6a48fd97ad1
Cr-Commit-Position: refs/heads/master@{#316677}