Google Git
Sign in
chromium/devtools/devtools-frontend/679fed80eb3bdc1e17e43cf421f5b1f0f2d22ea2
commit
679fed80eb3bdc1e17e43cf421f5b1f0f2d22ea2
[log]
author
Jack Franklin <jacktfranklin@chromium.org>
Thu Apr 25 09:58:34 2024
committer
Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>
Thu Apr 25 10:14:49 2024
tree
e594b16e55ca85e07791849ecf2ba13b27cd3587
parent
eb4d32e42310f42bb2e37e73ae1d25f1bcd94e0b [diff]
RPP: fix breadcrumbs test

This test assumed that a TraceBounds instance existed, but it might not
(unless some other test set one up). To fix, I ensure a new instance is
initialised with the right data in the test.

I've also added logging to catch if this happens in other tests so we
can easily fix in the future.

Bug: none
Change-Id: Icc3a16a08c29c01af8043e25f92637e817c001d3
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5485729
Auto-Submit: Jack Franklin <jacktfranklin@chromium.org>
Commit-Queue: Philip Pfaffe <pfaffe@chromium.org>
Commit-Queue: Jack Franklin <jacktfranklin@chromium.org>
Reviewed-by: Philip Pfaffe <pfaffe@chromium.org>
2 files changed
tree: e594b16e55ca85e07791849ecf2ba13b27cd3587
  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. .gitattributes
  22. .gitignore
  23. .gitmodules
  24. .gn
  25. .mailmap
  26. .npmignore
  27. .npmrc
  28. .style.yapf
  29. .stylelintignore
  30. .stylelintrc.json
  31. AUTHORS
  32. BUILD.gn
  33. codereview.settings
  34. DEPS
  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 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