We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi Paul, I've been trying out the devtools timeline (great work, it so nice to not parse the log) and it seems like scripting time is always low.
If I drag and drop the tracelog into Chrome 64 I get this:
And from devtools-timeline-model (model.bottomUpGroupBy('Category').children):
{ rendering: 1851.997999727726, scripting: 303.46600019931793, loading: 120.90799987316132, painting: 51.13799995183945 }
Here's the trace I used: https://gist.github.com/soulgalore/1946f6d3ed8da35c904e14c08985e172
Seen the same thing on other pages too. Could the reason be that it depends on an old chrome-devtools-frontend?
Best Peter
The text was updated successfully, but these errors were encountered:
Hi. Can you share the code for getting the timings info from model.bottomUpGroupBy('Category').children?
Sorry, something went wrong.
No branches or pull requests
Hi Paul,
I've been trying out the devtools timeline (great work, it so nice to not parse the log) and it seems like scripting time is always low.
If I drag and drop the tracelog into Chrome 64 I get this:
And from devtools-timeline-model (model.bottomUpGroupBy('Category').children):
Here's the trace I used: https://gist.github.com/soulgalore/1946f6d3ed8da35c904e14c08985e172
Seen the same thing on other pages too. Could the reason be that it depends on an old chrome-devtools-frontend?
Best
Peter
The text was updated successfully, but these errors were encountered: