Revert "[RPP Observations] Add phases for each interaction" This reverts commit a51d9f907b439d236bb53a9b4f6e6544c4637c9f. Reason for revert: e2e test on mac consistently fails since this CL landed. First failure: https://ci.chromium.org/ui/p/devtools-frontend/builders/ci/Stand-alone%20Mac-arm64/4134/overview. Original change's description: > [RPP Observations] Add phases for each interaction > > - Interaction list items are expandable > - Creates separate interaction if events happen in different frames > - Interactions are restored from the buffer > - `eventNames` property added to each interaction for future use > > Bug: 369097528, 365160880, 371052022 > Change-Id: Iab39cb300143aad3a6f2cc5ef5ecab79d7fd879e > Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5933344 > Reviewed-by: Paul Irish <paulirish@chromium.org> > Commit-Queue: Adam Raine <asraine@chromium.org> Bug: 369097528, 365160880, 371052022 Change-Id: I7cd208c5e2620c682f9babaec573df4c0880cfb6 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5938363 Auto-Submit: Simon Zünd <szuend@chromium.org> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
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/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.