Google Git
Sign in
chromium/devtools/devtools-frontend/f525f82e37a0cfce2283e5093d03cae64fc581c8
commit
f525f82e37a0cfce2283e5093d03cae64fc581c8
[log]
author
Jack Franklin <jacktfranklin@chromium.org>
Tue Jul 09 12:41:41 2024
committer
Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>
Tue Jul 09 13:31:15 2024
tree
c42b3c916a1145af6ede1f45caa7117ad7d03a9d
parent
b989a1ed8dd384235449d8f3aeed6c7c38428679 [diff]
Always initialise traceBounds in test

This tidies up some of the console noise when running the unit tests.

Historically we supported passing `false` here, but there's no need to
actually not-init the bounds manager, and the test modified here didn't
do it for any particular reason, so we might as well always do it, which
is good because it more closely aligns the tests with what happens in
reality when people use the perf panel.

Bug: none
Change-Id: Ieee39770c54c476f05628be4feb731d5f363b694
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5687957
Reviewed-by: Philip Pfaffe <pfaffe@chromium.org>
Auto-Submit: Jack Franklin <jacktfranklin@chromium.org>
Commit-Queue: Jack Franklin <jacktfranklin@chromium.org>
Commit-Queue: Philip Pfaffe <pfaffe@chromium.org>
2 files changed
tree: c42b3c916a1145af6ede1f45caa7117ad7d03a9d
  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. .eslintignore
  19. .eslintrc.js
  20. .git-blame-ignore-revs
  21. .gitallowed
  22. .gitattributes
  23. .gitignore
  24. .gitmodules
  25. .gn
  26. .mailmap
  27. .npmignore
  28. .npmrc
  29. .style.yapf
  30. .stylelintignore
  31. .stylelintrc.json
  32. AUTHORS
  33. BUILD.gn
  34. codereview.settings
  35. DEPS
  36. LICENSE
  37. OWNERS
  38. package-lock.json
  39. package.json
  40. PRESUBMIT.py
  41. README.md
  42. tsconfig.json
  43. 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 project documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.

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