[FCP++] Allow WebPerformance to report Largest/LastImagePaint
In order to report Largest/LastImagePaint to UKM, this CL is to plumb Largest/LastImagePaint to WebPerformance, but a follow-up CL has to be done to pick up the metric results from the browser side. Before this CL, the metrics report the result by dumping a trace event. This CL adds a new way of reporting. When the metrics fire new results. The results will be stored in the detector class. At the same time, the detector will notify web performance of the new result so that the web performance will pick up the metric results. This CL also refactors the OnLargest/LastImagePaintDetected function in ImagePaintTimingDetector for better readability. Bug: 869924 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I9b198b8bacac52e5dae66ea3ab9c2bedc56cfb8f Reviewed-on: https://chromium-review.googlesource.com/c/1280844Reviewed-by:Steve Kobes <skobes@chromium.org> Reviewed-by:
Bryan McQuade <bmcquade@chromium.org> Commit-Queue: Liquan (Max) Gǔ <maxlg@chromium.org> Cr-Commit-Position: refs/heads/master@{#599976}
Showing
Please register or sign in to comment