CC: Allow per-curve timing functions to be steps timing functions

CC: Allow per-curve timing functions to be steps timing functions

Implement per-curve timing functions.
A chromium part. Blink part: https://codereview.chromium.org/800133004

In general: Allow Web Animations with Animation timing functions to run on compositor.

BUG=417909
R=dstockwell@chromium.org
R=ajuma@chromium.org
TEST=ManualTests/animation/compositor-animation-steps.html

Committed: https://crrev.com/5dce43319fa35c84218f7d4396a8dd6383046338
Cr-Commit-Position: refs/heads/master@{#310203}

[ajuma, 2015-01-05 15:44:54]

lgtm, but please update the patch title/description to describe what this
particular patch does (in addition to why it's needed) -- this particular patch
allows per-curve timing functions to be steps timing functions.

[loyso (OOO), 2015-01-06 00:25:45]

On 2015/01/05 15:44:54, ajuma wrote:
> lgtm, but please update the patch title/description to describe what this
> particular patch does (in addition to why it's needed) -- this particular
patch
> allows per-curve timing functions to be steps timing functions.

done!

[dstockwell, 2015-01-06 03:31:08]

On 2015/01/06 at 00:25:45, loyso wrote:
> On 2015/01/05 15:44:54, ajuma wrote:
> > lgtm, but please update the patch title/description to describe what this
> > particular patch does (in addition to why it's needed) -- this particular
patch
> > allows per-curve timing functions to be steps timing functions.
> 
> done!

lgtm, but I still don't think the description is quite right. Seems like some
support for whole-curve timing functions was already existing (r297147), this
patch refactors that to add support for step.

[dstockwell, 2015-01-06 03:46:07]

On 2015/01/06 at 03:31:08, dstockwell wrote:
> On 2015/01/06 at 00:25:45, loyso wrote:
> > On 2015/01/05 15:44:54, ajuma wrote:
> > > lgtm, but please update the patch title/description to describe what this
> > > particular patch does (in addition to why it's needed) -- this particular
patch
> > > allows per-curve timing functions to be steps timing functions.
> > 
> > done!
> 
> lgtm, but I still don't think the description is quite right. Seems like some
support for whole-curve timing functions was already existing (r297147), this
patch refactors that to add support for step.

I didn't notice that the title in the review tool had been updated, it should be
replicated on the first line of the description.

[loyso (OOO), 2015-01-06 03:51:38]

On 2015/01/06 03:46:07, dstockwell wrote:
> On 2015/01/06 at 03:31:08, dstockwell wrote:
> > On 2015/01/06 at 00:25:45, loyso wrote:
> > > On 2015/01/05 15:44:54, ajuma wrote:
> > > > lgtm, but please update the patch title/description to describe what
this
> > > > particular patch does (in addition to why it's needed) -- this
particular
> patch
> > > > allows per-curve timing functions to be steps timing functions.
> > > 
> > > done!
> > 
> > lgtm, but I still don't think the description is quite right. Seems like
some
> support for whole-curve timing functions was already existing (r297147), this
> patch refactors that to add support for step.
> 
> I didn't notice that the title in the review tool had been updated, it should
be
> replicated on the first line of the description.

Thanks, fixed!

[loyso (OOO), 2015-01-07 00:58:56]

The CQ bit was checked by loyso@chromium.org

[commit-bot: I haz the power, 2015-01-07 00:59:22]

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

[commit-bot: I haz the power, 2015-01-07 01:12:51]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-01-07 01:13:52]

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