Google Git
Sign in
chromium / devtools / devtools-frontend / 1ed1a225270d499776a5f0d58cda4bbb1fd08145
commit1ed1a225270d499776a5f0d58cda4bbb1fd08145[log] [tgz]
authorElorm Coch <elormcoch@microsoft.com>Tue Apr 22 16:08:45 2025
committerDevtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Apr 22 16:51:18 2025
tree26dedc7f942dc594155ca989babc859fdf9c15db
parent45238b215dc1ee1bc5a3eb5870f7623b708b1136 [diff]
Fix DOMBreakpoints duplicating on refresh and not persisting toggled state upon page reload

Issue: DOM breakpoints don't deduplicate or persist their enabled state
on page reload. https://imgur.com/a/3LUjYNn

Upon page reload, documentUpdated fires which calls appendBreakpoint.
Before, we would end up creating a new breakpoint for the same
breakpoint type and for the same node, thus creating duplicate
breakpoints.

Also, saveDOMBreakpoint needs to be called upon toggle to update the
breakpoint setting so we persist state between page reloads.

Bug: 411163945
Change-Id: Icb2ba93b304dc1492e14ad02e9fd61764882e024
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6466456
Commit-Queue: Sylvester Elorm Coch <elormcoch@microsoft.com>
Reviewed-by: Simon Zünd <szuend@chromium.org>
4 files changed
tree: 26dedc7f942dc594155ca989babc859fdf9c15db
  1. .vscode/
  2. build_overrides/
  3. config/
  4. docs/
  5. extension-api/
  6. extensions/
  7. front_end/
  8. inspector_overlay/
  9. node_modules/
  10. scripts/
  11. test/
  12. third_party/
  13. v8/
  14. build
  15. buildtools
  16. .clang-format
  17. .editorconfig
  18. .git-blame-ignore-revs
  19. .gitallowed
  20. .gitattributes
  21. .gitignore
  22. .gitmodules
  23. .gn
  24. .mailmap
  25. .npmignore
  26. .npmrc
  27. .style.yapf
  28. .stylelintignore
  29. .stylelintrc.json
  30. AUTHORS
  31. BUILD.gn
  32. codereview.settings
  33. CONTRIBUTING.md
  34. DEPS
  35. eslint.config.mjs
  36. favicon.ico
  37. LICENSE
  38. OWNERS
  39. package-lock.json
  40. package.json
  41. PRESUBMIT.py
  42. README.md
  43. tsconfig.json
  44. 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: