RPP: Remove ThreadTracksSource.BOTH_ENGINEs and update screenshots This is the first in a long set of CLs that will begin to remove old engine functionality we do not need. I have started with the ThreadTracksSource enum and removed the BOTH_ENGINES flag; updating all the screenshot tests to use the new engine exclusively. In future CLs I will remove the enum and the flag entirely, but first I will go through and remove code that only runs for the OLD_ENGINE flag. Bug: 1499182 Change-Id: I7ab164e500576d044f334705d5e99649b3523e94 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5002389 Reviewed-by: Andres Olivares <[email protected]> Auto-Submit: Jack Franklin <[email protected]> Commit-Queue: Andres Olivares <[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 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: [email protected]
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools