| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
if (base::StartsWith(name, "PageLoad.Internal.",@lin...@chromium.org Do you know what kind of metrics are recorded as "PageLoad.Internal"? I saw you added multiple prerender related metrics here.
"PageLoad.PaintTiming.NavigationToFirstContentfulPaint.WebUI",I'm not sure if this direction is a correct approach. `PageLoad.PaintTiming.NavigationToFirstContentfulPaint.WebUI` is recorded on the page visit if the page is built with the WebUI right?
This implies that the new WebUI based reload button effects existing `PageLoad.PaintTiming.NavigationToFirstContentfulPaint.WebUI` metrics, and that makes the metric less reliable. Rather than excluding the metric here, I feel it's better to record the page load metrics for the WebUI based reload button separately, and not to record `PageLoad.PaintTiming.NavigationToFirstContentfulPaint.WebUI/NonTabWebUI`. What do you think?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
"PageLoad.PaintTiming.NavigationToFirstContentfulPaint.WebUI",I'm not sure if this direction is a correct approach. `PageLoad.PaintTiming.NavigationToFirstContentfulPaint.WebUI` is recorded on the page visit if the page is built with the WebUI right?
This implies that the new WebUI based reload button effects existing `PageLoad.PaintTiming.NavigationToFirstContentfulPaint.WebUI` metrics, and that makes the metric less reliable. Rather than excluding the metric here, I feel it's better to record the page load metrics for the WebUI based reload button separately, and not to record `PageLoad.PaintTiming.NavigationToFirstContentfulPaint.WebUI/NonTabWebUI`. What do you think?
Thanks, +1 to introducing separate metrics. As we will work on adding metrics stuff later together, I'll leave this cl for a while.
"PageLoad.PaintTiming.NavigationToFirstContentfulPaint.WebUI",I'm not sure if this direction is a correct approach. `PageLoad.PaintTiming.NavigationToFirstContentfulPaint.WebUI` is recorded on the page visit if the page is built with the WebUI right?
This implies that the new WebUI based reload button effects existing `PageLoad.PaintTiming.NavigationToFirstContentfulPaint.WebUI` metrics, and that makes the metric less reliable. Rather than excluding the metric here, I feel it's better to record the page load metrics for the WebUI based reload button separately, and not to record `PageLoad.PaintTiming.NavigationToFirstContentfulPaint.WebUI/NonTabWebUI`. What do you think?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
if (base::StartsWith(name, "PageLoad.Internal.",Lingqi Chi@lin...@chromium.org Do you know what kind of metrics are recorded as "PageLoad.Internal"? I saw you added multiple prerender related metrics here.
IIRC, we use PageLoad.Internal for debugging and validation, so they are supposed to be short-lived, (but unfortunately some tasks are postponed so we just keep recording these metrics = =)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |