TimelineModel: adjust for changes in utility process main thread naming. This got changed in https://chromium-review.googlesource.com/c/chromium/src/+/4129799, so some of these threads weren't found, resulting in https://github.com/WICG/turtledove/issues/499 Bug: 1432954 Change-Id: I59a235ed3ddeb5c6e2afbefaf8449f3ef4833f87 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4414780 Reviewed-by: Victor Porof <victorporof@chromium.org> Reviewed-by: Jack Franklin <jacktfranklin@chromium.org> Commit-Queue: Maks Orlovich <morlovich@chromium.org> (cherry picked from commit 4a76ee94bde3cba8d28617b86187c9e819176e58) Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4436689 Commit-Queue: Paul Jensen <pauljensen@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com.
Check out the project 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.
All DevTools commits: View the log or follow @DevToolsCommits on Twitter
All open DevTools tickets on crbug.com
File a new DevTools ticket: new.crbug.com
Code reviews mailing list: devtools-reviews@chromium.org
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools