diff options
| author | vadimt <vadimt@chromium.org> | 2015-04-27 14:43:02 -0700 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-04-27 21:47:22 +0000 |
| commit | e2de4734b01f37454f939bc493a8a5cb59ce3c42 (patch) | |
| tree | 11892c061e458a6459753f69328ec7ff06c880a5 /components/metrics.gypi | |
| parent | 84a3918452ae67b24bc60acdf7abd7b226879a5e (diff) | |
| download | chromium_src-e2de4734b01f37454f939bc493a8a5cb59ce3c42.zip chromium_src-e2de4734b01f37454f939bc493a8a5cb59ce3c42.tar.gz chromium_src-e2de4734b01f37454f939bc493a8a5cb59ce3c42.tar.bz2 | |
Delivering the FIRST_NONEMPTY_PAINT phase changing event to base/. This concludes the client-side “phased profiling” work.
I’m removing TODO items, and the DIFFS introduced by this should remind the reviewers that there are open questions that they wanted to re-raise, assuming the the CL doesn’t make it clear that the way it’s implemented is OK.
If there are still concerns, we should agree on one important thing before we resume the discussions: phase change delivery chain doesn’t go through metrics provider. It starts at the event source (FirstWebContentsProfiler), then goes to TrackingSynchronizer, then goes to base/. Once we agree on the design of this chain, it will make sense to go to more detailed discussions and open questions.
BUG=456354
Review URL: https://codereview.chromium.org/1021053003
Cr-Commit-Position: refs/heads/master@{#327143}
Diffstat (limited to 'components/metrics.gypi')
| -rw-r--r-- | components/metrics.gypi | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/components/metrics.gypi b/components/metrics.gypi index ddad096..45a36d1 100644 --- a/components/metrics.gypi +++ b/components/metrics.gypi @@ -148,6 +148,7 @@ 'metrics/profiler/profiler_metrics_provider.h', 'metrics/profiler/tracking_synchronizer.cc', 'metrics/profiler/tracking_synchronizer.h', + 'metrics/profiler/tracking_synchronizer_observer.cc', 'metrics/profiler/tracking_synchronizer_observer.h', ], }, |