[sources] Migrate CallStackSidebarPane to new StackTrace This CL changes the CallStackSidebarPane to create a fresh StackTrace instance on every pause. Rather then creating a LiveLocation for each frame and updating them in-place, we listen for UPDATE events and just re-render the whole pane. This is not necessarily more expensive: An UPDATE event comes only once when e.g. a new source map is attached, not separately for every frame. To make this work, we need to disable the "expandCallFrame" callback from the language plugin. This is handled by the 'translateFrameStep' cleanly now. Follow-up updates can remove the "expandCallFrame" layering violation as well as "createCallFrameLiveLocation". R=pfaffe@chromium.org Fixed: 465879478 Change-Id: I334955fbc5e6da0e326f9da5fd4ea21c616670bb Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/7531559 Commit-Queue: Simon Zünd <szuend@chromium.org> Reviewed-by: Philip Pfaffe <pfaffe@chromium.org>
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.