[M135] Do not create toolbar item on the subsequent connectedCallback invocations


Otherwise we end up with repeated icons.

Bug: 400939386
Fixed: 400950563
Change-Id: I2f6b886262b7e5374c28c21dfacfd26bbaf00847
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6328141
Auto-Submit: Danil Somsikov <dsv@chromium.org>
Commit-Queue: Danil Somsikov <dsv@chromium.org>
Reviewed-by: Alex Rudenko <alexrudenko@chromium.org>
(cherry picked from commit ad32212dc354cea4c40e2ae8a86f14441ce87d17)
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6333533
1 file changed
tree: a542b7d6f200a155787a12446a28ac2c7c2c4293
  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. .clang-format
  15. .editorconfig
  16. .git-blame-ignore-revs
  17. .gitallowed
  18. .gitattributes
  19. .gitignore
  20. .gitmodules
  21. .gn
  22. .mailmap
  23. .npmignore
  24. .npmrc
  25. .style.yapf
  26. .stylelintignore
  27. .stylelintrc.json
  28. AUTHORS
  29. BUILD.gn
  30. codereview.settings
  31. CONTRIBUTING.md
  32. DEPS
  33. eslint.config.mjs
  34. favicon.ico
  35. LICENSE
  36. OWNERS
  37. package-lock.json
  38. package.json
  39. PRESUBMIT.py
  40. README.md
  41. tsconfig.json
  42. 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: