RPP: use "local metrics" and "field metrics" consistently

This changes it because before we had "Live metrics" and "Field data" as
the prominent terms, and that's a bit of a mixup.

This CL makes us consistently use:

- Local metrics
- Field metrics

Which is consistent; and avoids any confusion of "live metrics" which is
not as clear as "Local metrics".

To avoid confusion regarding the title of the view itself, we keep the
title of the page to "Live metrics". So the way to think about this is:

1. We have a **Live metrics** page
2. That shows both **local metrics** and **field metrics** (if
   configured).

(Thanks to @barrypollard for his input).

R=paulirish@chromium.org

Fixed: 404513461
Change-Id: Ief19e37ac4968d4fe47a6e58c40983dfeefd8986
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6624111
Reviewed-by: Paul Irish <paulirish@chromium.org>
Auto-Submit: Jack Franklin <jacktfranklin@chromium.org>
Commit-Queue: Jack Franklin <jacktfranklin@chromium.org>
6 files changed
tree: 9f97debd420f909b30933a70ff47a0d2ce7a0f0d
  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. .clang-format-ignore
  16. .editorconfig
  17. .git-blame-ignore-revs
  18. .gitallowed
  19. .gitattributes
  20. .gitignore
  21. .gitmodules
  22. .gn
  23. .mailmap
  24. .npmignore
  25. .npmrc
  26. .style.yapf
  27. .stylelintignore
  28. .stylelintrc.json
  29. AUTHORS
  30. BUILD.gn
  31. codereview.settings
  32. CONTRIBUTING.md
  33. DEPS
  34. DIR_METADATA
  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. 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: