[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>
5 files changed
tree: 9938021393b23c90686d0d8acb248a7f02afade8
  1. .gemini/
  2. .github/
  3. .vscode/
  4. agents/
  5. build_overrides/
  6. config/
  7. docs/
  8. extension-api/
  9. extensions/
  10. front_end/
  11. inspector_overlay/
  12. mcp/
  13. node_modules/
  14. scripts/
  15. test/
  16. third_party/
  17. v8/
  18. .clang-format
  19. .clang-format-ignore
  20. .editorconfig
  21. .env.template
  22. .geminiignore
  23. .git-blame-ignore-revs
  24. .gitallowed
  25. .gitattributes
  26. .gitignore
  27. .gitmodules
  28. .gn
  29. .mailmap
  30. .npmignore
  31. .npmrc
  32. .style.yapf
  33. .stylelintignore
  34. .stylelintrc.json
  35. AUTHORS
  36. BUILD.gn
  37. codereview.settings
  38. CONTRIBUTING.md
  39. DEPS
  40. DIR_METADATA
  41. eslint.config.mjs
  42. favicon.ico
  43. LICENSE
  44. OWNERS
  45. package-lock.json
  46. package.json
  47. PRESUBMIT.py
  48. README.md
  49. WATCHLISTS
README.md

Chrome DevTools frontend

npm package

The client-side of the Chrome DevTools, including all TypeScript & CSS to run the DevTools webapp.

Source code and documentation

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.

Source mirrors

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.

Getting in touch

There are a few options to keep an eye on the latest and greatest of DevTools development: