Move core/animation timers to frame-specific task runners.

Move core/animation timers to frame-specific task runners.

Some animation events are dispatched on the DOM manipulation task
source. However, the spec [1] doesn't seem to say much about timelines
and their animations, so dispatch them on the unspeced timer source.

[1] https://w3c.github.io/web-animations/#document-timelines

BUG=624694
Committed: https://crrev.com/d1f518fa9e5e4b96b5942b90767272377cbadbb7
Cr-Commit-Position: refs/heads/master@{#441306}

[dcheng, 2017-01-04 01:25:02]

dcheng@chromium.org changed reviewers:
+ alancutter@chromium.org

[dcheng, 2017-01-04 01:25:02]

The web animations spec was the closest thing I could find that documents this,
and it doesn't seem particularly clear which task source drives animation
timelines...

[dcheng, 2017-01-04 01:48:36]

The CQ bit was checked by dcheng@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-01-04 01:48:51]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[alancutter (OOO until 2018), 2017-01-04 02:00:13]

rs lgtm.

[dcheng, 2017-01-04 02:12:40]

The CQ bit was unchecked by dcheng@chromium.org

[dcheng, 2017-01-04 02:12:41]

The CQ bit was checked by dcheng@chromium.org

[commit-bot: I haz the power, 2017-01-04 02:13:14]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-01-04 03:18:07]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1483495961324410, "parent_rev":
"5cbc45f3e8104fa277222d03c5531e3e78cfbe2e", "commit_rev":
"7edef7ca232fd589e24e294c035627f4b33aaba1"}

[commit-bot: I haz the power, 2017-01-04 03:18:35]

Description was changed from

==========
Move core/animation timers to frame-specific task runners.

Some animation events are dispatched on the DOM manipulation task
source. However, the spec [1] doesn't seem to say much about timelines
and their animations, so dispatch them on the unspeced timer source.

[1] https://w3c.github.io/web-animations/#document-timelines

BUG=624694
==========

to

==========
Move core/animation timers to frame-specific task runners.

Some animation events are dispatched on the DOM manipulation task
source. However, the spec [1] doesn't seem to say much about timelines
and their animations, so dispatch them on the unspeced timer source.

[1] https://w3c.github.io/web-animations/#document-timelines

BUG=624694

Review-Url: https://codereview.chromium.org/2616593002
==========

[commit-bot: I haz the power, 2017-01-04 03:18:36]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2017-01-04 03:21:18]

Description was changed from

==========
Move core/animation timers to frame-specific task runners.

Some animation events are dispatched on the DOM manipulation task
source. However, the spec [1] doesn't seem to say much about timelines
and their animations, so dispatch them on the unspeced timer source.

[1] https://w3c.github.io/web-animations/#document-timelines

BUG=624694

Review-Url: https://codereview.chromium.org/2616593002
==========

to

==========
Move core/animation timers to frame-specific task runners.

Some animation events are dispatched on the DOM manipulation task
source. However, the spec [1] doesn't seem to say much about timelines
and their animations, so dispatch them on the unspeced timer source.

[1] https://w3c.github.io/web-animations/#document-timelines

BUG=624694

Committed: https://crrev.com/d1f518fa9e5e4b96b5942b90767272377cbadbb7
Cr-Commit-Position: refs/heads/master@{#441306}
==========

[commit-bot: I haz the power, 2017-01-04 03:21:19]

Patchset 1 (id:??) landed as
https://crrev.com/d1f518fa9e5e4b96b5942b90767272377cbadbb7
Cr-Commit-Position: refs/heads/master@{#441306}