commit | babc50a33ad4362d4ffa81a03038fa547c1c66f7 | [log] [tgz] |
---|---|---|
author | Jack Franklin <jacktfranklin@chromium.org> | Fri Mar 03 16:20:34 2023 |
committer | Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Mar 06 08:30:02 2023 |
tree | 4c72a86fae0974ba48d316a0d3d2d90c4e16f8b5 | |
parent | 243c545bd8b64de70e71e7ee8f7aac0b85599d3e [diff] |
Set isFreshRecording correctly for new trace engine Bug: 1406847 Change-Id: Ib2350c00bee4c709f4adc3656be328267b1c12c3 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4307576 Auto-Submit: Jack Franklin <jacktfranklin@chromium.org> Commit-Queue: Andres Olivares <andoli@chromium.org> Reviewed-by: Andres Olivares <andoli@chromium.org>
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