GitLab

As revealed in the discussion in the reported bug, ash::FpsCounter
and ui::AnimationMetricsReporter calculates a slightly different
data points. For this specific case, ui::AnimationMetricsReporter
would be better.

Note that this does not recover the reported number to the original;
Ash.WindowCycleView.AnimationSmoothness.Show.2windows to be ~50
and slightly shorter than previous value (~67), but this would
mean that ash::FpsCounter wouldn't be good for computing
animation smoothness.

Bug: 1085501
Test: tast ui.WindowCycleView on coral/astronaut
Change-Id: I747d5eeaaeb2c319fbe661e8c1d4b6f8c67ec296
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2212492Reviewed-by: Sammie Quon <sammiequon@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Jun Mukai <mukai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#771951}