Adriana Ixba
3067d40135
This also simplifies the insight shape closer to how we use it in RPP, and how we will use it in LH. This also simplifies some tests. This modifies how we generate eventIDs when grouping by 3P. This fixes a bug where when grouping by 3P, generateEventID can incorrectly group events of different entities. This fixes: - misalignment in main thread times insight<->3P table (by using same data source, including instant events, filters) - incorrect event grouping: breaking bottomUp button and causing further incorrect selftime/transfersize (bottomUp tree node ID generation) Bug: 394651390 Change-Id: I1660a5b5b9a90be89815aad858caea94f153eabb Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6341914 Reviewed-by: Paul Irish <paulirish@chromium.org> Commit-Queue: Paul Irish <paulirish@chromium.org>
Chrome DevTools frontend
The client-side of the Chrome DevTools, including all TypeScript & CSS to run the DevTools webapp.
Source code and documentation
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 user documentation: devtools.chrome.com
- Debugger protocol documentation: chromedevtools.github.io/devtools-protocol
- Awesome Chrome DevTools: github.com/paulirish/awesome-chrome-devtools
- Contributing to Chrome DevTools: goo.gle/devtools-contribution-guide
- Contributing To Chrome DevTools Protocol: goo.gle/devtools-contribution-guide-cdp
Source mirrors
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.
Getting in touch
- @ChromeDevTools on Twitter
- Chrome DevTools mailing list: g/google-chrome-developer-tools
- File a new DevTools ticket: goo.gle/devtools-bug
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/devtools-reviews@chromium.org 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.