Google Git
Sign in
chromium/devtools/devtools-frontend/da3c3e6d039cb05610366111e37e1c7c91d400a2
commit
da3c3e6d039cb05610366111e37e1c7c91d400a2
[log]
author
Andrés Olivares <andoli@chromium.org>
Mon Mar 24 19:11:47 2025
committer
Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>
Tue Mar 25 15:07:04 2025
tree
d425ae2426c249f935ff8852b6814388988ca9f8
parent
5013142f4f4af31ca08d296235657c22ace1a0e6 [diff]
[Perf panel] Remove support for experimental server timings track

We did not receive clear signal about the usefulness of having a mechanism to display server timings in the client timeline.

Developers will still be able to see server timings in the details of network requests (as of https://crrev.com/c/6387100) and if needed, a server timing track could be injected using the extensibility API. (granted, a mechanisim to map server timestamps to the client clock needs to be implemented, but this doesn't seem to be a big constraint as devs are alreading doing so, like React).

Bug: 403223638
Change-Id: I10d80fe10598dcf7c3014cfc1fcbce03b6024fb5
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6387102
Reviewed-by: Jack Franklin <jacktfranklin@chromium.org>
Commit-Queue: Andres Olivares <andoli@chromium.org>
21 files changed
tree: d425ae2426c249f935ff8852b6814388988ca9f8
  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: