New issue
Advanced search Search tips

Issue 673922 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Oct 31
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

Improvements to DevTools first*Paint metrics

Project Member Reported by ericbidelman@chromium.org, Dec 13 2016

Issue description

Chrome Version: 57.0.2950.0
OS: MacOS x

What steps will reproduce the problem?
(0) Have the "Show all events in Timeline" DT experiment on.
(1) Visit https://www.chromestatus.com/features
(2) Take a page load timeline recording and drill into event log.
(3) Filter on "first"

What is the expected result?

See the screenshot. I would expect the first*Paint metrics be attributed to green paint operations. These metrics should also have attribute to what frame/document they came from.

It's worth noting that chromestatus.com does not use iframes but it does use HTML Imports, so there are multiple documents on the page. Could that explain why there are multiple firstContentPaints and firstPaints?

Current:

The event metrics are classified as scripting. They also do not have attribution on what caused them.
 
Screen Shot 2016-12-13 at 2.26.14 PM.png
113 KB View Download
Owner: caseq@chromium.org
Status: Assigned (was: Untriaged)
Components: -Platform>DevTools>Performance>Tracing Platform>DevTools>Performance
Status: Archived (was: Assigned)
Bulk closing low-priority issues with no activity. Please re-file and refer to the closed issue if it's essential to fix.

Sign in to add a comment