-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
core(render-blocking): use trace engine as the source of truth #15839
Conversation
Did you assess the differences between our logic in TabsBlockingFirstPaint and using the blink signal? ref #2065 (comment) |
I verified that our expectations in dbw smoke test are the same but did not inspect the raw data. |
Looks like this is working, but we will need to wait for M123 to be stable before we think about shipping this |
@@ -829,6 +829,9 @@ class TraceProcessor { | |||
/** @param {number=} ts */ | |||
const maybeGetTiming = (ts) => ts === undefined ? undefined : getTiming(ts); | |||
|
|||
const navigationId = timeOriginEvt.args.data?.navigationId; | |||
if (!navigationId) throw new Error('No navigation ID'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Several old traces don't have this event...so may need to update them or do a workaround
#2065
https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5250877
Uses the new
RenderBlocking
insight in the trace engine to find render blocking requests. Also eliminates the need for theTagsBlockingFirstPaint
artifact.