RPP: Support columns, pretty'd sources in Source's panel profile data
The profile data decorations in the Sources panel now apply to the '-'
lines in Sources when a minified file is pretty-printed, and correctly
for minified + source map'd scripts.
The Sources panel displays profile data ("x ms") in the line gutters
when a performance trace is active. However, we did not handle common
edge cases involving pretty-formatted files (the `{}` button), nor did
we handle source mapped content well (we totally ignored column
information, and since most generated code is minified across few lines,
profile data would be displayed far too coarsely).
Now, we utilize the pretty -> original line mapping to create accurate
profile data for the formatted code; and further we consider the column
when mapping the profile data to a UILocation.
Bug: 406012441
Change-Id: I84278eec4e778c62f8568e2c96353fa98be92b32
Bypass-Check-License: test fixture cannot have the license without breaking the test. (because isMinified)
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6588993
Commit-Queue: Paul Irish <[email protected]>
Reviewed-by: Connor Clark <[email protected]>
The client-side of the Chrome DevTools, including all TypeScript & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com. Check out the Chromium DevTools documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.
DevTools frontend repository is mirrored on GitHub.
DevTools frontend is also available on NPM as the chrome-devtools-frontend package. It's not currently available via CJS or ES modules, so consuming this package in other tools may require some effort.
The version number of the npm package (e.g. 1.0.373466) refers to the Chromium commit position of latest frontend git commit. It's incremented with every Chromium commit, however the package is updated roughly daily.
There are a few options to keep an eye on the latest and greatest of DevTools development:
Follow What's new in DevTools.
Follow Umar's Dev Tips.
Follow these individual Twitter accounts: @umaar, @malyw, @kdzwinel, @addyosmani, @paul_irish, @samccone, @mathias, @mattzeunert, @PrashantPalikhe, @ziyunfei, and @bmeurer.
Follow to g/[email protected] mailing list for all reviews of pending code, and view the log, or follow @DevToolsCommits on Twitter.
Checkout all open DevTools tickets on crbug.com
Use Chrome Canary and poke around the experiments.