Google Git
Sign in
chromium / devtools / devtools-frontend / refs/heads/chromium/4211
commit038b9b33775be9de430187e33529fdd8b696fdb9[log] [tgz]
authorKim-Anh Tran <[email protected]>Mon Jul 20 06:40:09 2020
committerCommit Bot <[email protected]>Thu Jul 23 09:00:38 2020
tree40a9e372aba64bc5c78b19761df54ec30d8a64db
parentaf6416cd74c82508435cc34e5c5557484be68c59 [diff]
Use setBreakpoint() only when creating a new breakpoint

Up until now we used getPossibleBreakpoints() in order to find the
breakable location, just for setBreakpoint to set a breakpoint
on the first returned location. Using setBreakpoint() directly
is more intuitive and straight-forward, and for our use case
it should result in the same breakpoint setting behavior.

Bug: chromium:1105172
Change-Id: Id9460dcddb714fafa32a4620116e29c62c03c301
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2306150
Auto-Submit: Kim-Anh Tran <[email protected]>
Reviewed-by: Benedikt Meurer <[email protected]>
Commit-Queue: Benedikt Meurer <[email protected]>
1 file changed
tree: 40a9e372aba64bc5c78b19761df54ec30d8a64db
  1. back_end/
  2. build_overrides/
  3. docs/
  4. front_end/
  5. node_modules/
  6. scripts/
  7. test/
  8. third_party/
  9. v8/
  10. .clang-format
  11. .editorconfig
  12. .eslintignore
  13. .eslintrc.js
  14. .gitattributes
  15. .gitignore
  16. .gn
  17. .npmignore
  18. .npmrc
  19. .style.yapf
  20. .stylelintignore
  21. .stylelintrc.json
  22. all_devtools_files.gni
  23. all_devtools_modules.gni
  24. AUTHORS
  25. BUILD.gn
  26. COMMON_OWNERS
  27. DEPS
  28. devtools_image_files.gni
  29. devtools_module_entrypoints.gni
  30. ENG_REVIEW_OWNERS
  31. INFRA_OWNERS
  32. LICENSE
  33. LIGHTHOUSE_OWNERS
  34. OWNERS
  35. package-lock.json
  36. package.json
  37. PRESUBMIT.py
  38. protocol.json
  39. README.md
  40. tsconfig.base.json
  41. tsconfig.json
  42. WATCHLISTS
README.md

Chrome DevTools frontend

npm package

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

Source code

The frontend is available on chromium.googlesource.com.

Design guidelines

Please be aware that DevTools follows additional development guidelines.

Issue triage

The issue triage guidelines can be found here.

Workflows

Instructions to set up, use, and maintain a DevTools frontend checkout can be found here.

Additional references

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