[ntp][modules] Log max ratio of a module visible to the user The max ratio is logged upon NTP unload and has perdecage (x/10th) granularity. The max ratio is logged with the chrome.metricsPrivate API, which this CL enables on chrome://new-tab-page. Other NTP metrics are logged via custom renderer -> browser Mojo calls. However, we decided to employ chrome.privateMetrics in this CL since there is a potential race condition between page unload and the custom Mojo calls. In the future we will likely migrate our other metrics to chrome.privateMetrics as well. Bug: 1166865 Change-Id: I32f98b0cdb7caaab25194c556bff9911f0b1c116 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631201 Reviewed-by: Moe Ahmadi <mahmadi@chromium.org> Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org> Reviewed-by: Mark Pearson <mpearson@chromium.org> Auto-Submit: Tibor Goldschwendt <tiborg@chromium.org> Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> Cr-Commit-Position: refs/heads/master@{#847335}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.