Track loading behavior from Blink and expose to //content and consumers |
|||||
Issue descriptionThere are many useful loading signals that Blink is aware of that would be useful to expose to the page_load_metrics system. One example of such a signal would be "did Blink use a codepath pertinent to some experiment X?" This approach will allow us to separate histograms by very fine grained details. The first step would be to thread a loading behavior enum into RenderFrameObserver. Then, we can integrate it into the page_load_metrics RenderFrameObserver and send a packed flag up via IPC. The first part of this work landed here: https://codereview.chromium.org/1846143003
,
Apr 11 2016
This CL just exposes data for metrics collection. We also plan on merging the related CL https://codereview.chromium.org/1857443002/. These metrics will be very useful for experiments we are running in M51.
,
Apr 12 2016
Your change meets the bar and is auto-approved for M51 (branch: 2704)
,
Apr 12 2016
Hi tinazh@, this change exposed a flaky layout test. I've since added an expectation of failure temporarily for the test. Does that need to be merged as well before this one? https://codereview.chromium.org/1880893002/
,
Apr 12 2016
actually ccing tinazh@.
,
Apr 15 2016
Going to merge this in now.
,
Apr 29 2016
This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible! If all merges have been completed, please remove any remaining Merge-Approved labels from this issue. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 29 2016
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by sshru...@google.com
, Apr 11 2016