Google GitGoogle Git
Sign in
chromium/devtools/devtools-frontend/63cb68b52adc40fb3cc88689cc1b91c26db9d83a
commit
63cb68b52adc40fb3cc88689cc1b91c26db9d83a
[log]
author
Simon Zünd <szuend@chromium.org>
Mon Oct 05 13:17:03 2026
committer
devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>
Mon Oct 05 16:02:41 2026
tree
996f95cf02c7822e6dd5e55dc7c12bd4570d6c5e
parent
1186aaa50578bdb4a8858eb768111224032e50a9 [diff]
[sdk] Pass the StepContext to the before-paused callback

Logical stepping series, CL 12/23.

The callback receives the full `StepContext` instead of the derived
Wasm auto-stepping context (the function location of the frame a step
over started in). Deriving the latter moves into
`DebuggerWorkspaceBinding.#shouldPauseInWasm`, the only user. Source
map stepping needs the mode and the original call frames.

No behavior change.

R=pfaffe@chromium.org

Bug: 569693470
Change-Id: I02ba019cfa3cba9c387297f9bce8bce03f820a3b
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/8499927
Reviewed-by: Philip Pfaffe <pfaffe@chromium.org>
Commit-Queue: Simon Zünd <szuend@chromium.org>
2 files changed
tree: 996f95cf02c7822e6dd5e55dc7c12bd4570d6c5e
  1. .agents/
  2. .gemini/
  3. .github/
  4. .vscode/
  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. build
  19. buildtools
  20. .clang-format
  21. .clang-format-ignore
  22. .editorconfig
  23. .env.template
  24. .geminiignore
  25. .git-blame-ignore-revs
  26. .gitallowed
  27. .gitattributes
  28. .gitignore
  29. .gitmodules
  30. .gn
  31. .mailmap
  32. .npmignore
  33. .npmrc
  34. .style.yapf
  35. .stylelintignore
  36. .stylelintrc.json
  37. AUTHORS
  38. BUILD.gn
  39. codereview.settings
  40. CONTRIBUTING.md
  41. DEPS
  42. DIR_METADATA
  43. eslint.config.mjs
  44. favicon.ico
  45. LICENSE
  46. OWNERS
  47. package-lock.json
  48. package.json
  49. PRESUBMIT.py
  50. README.md
  51. SECURITY.md
  52. 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: