[go: nahoru, domu]
Google Git
Sign in
chromium / devtools / devtools-frontend / 5bd9ee599b03661993f732225f0c7b867d353110
commit5bd9ee599b03661993f732225f0c7b867d353110[log] [tgz]
authorAndrés Olivares <andoli@chromium.org>Tue Feb 28 10:18:10 2023
committerDevtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Feb 28 11:07:22 2023
treeecf4176cf413d3799c67749b3438e29e5d2a47f9
parent81fd2c826ff0c205c6ca076f2ec526c38a9e65bb [diff]
[RPP] Add support for marker events in PageLoadMetricsHandler

Marker events are page load events that have no duration and that appear
in the Timings track. For example, largest contentful paint,
MarkDomContent DomContentLoad, etc. Although the PageLoadMetricsHandler
buffered some of these, they were not exported and not all marker event
types were buffered (like the Load event).

So that we can use the new engine in the Timings track, this CL adds
support for marker events in the handler by buffering and exporting all
the marker events in a trace.

Bug: 1409044
Change-Id: Ifb0a231f1818f02357af21797d24cca733b70892
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4280823
Reviewed-by: Nancy Li <nancyly@chromium.org>
Commit-Queue: Andres Olivares <andoli@chromium.org>
3 files changed
tree: ecf4176cf413d3799c67749b3438e29e5d2a47f9
  1. .vscode/
  2. build_overrides/
  3. config/
  4. docs/
  5. extension-api/
  6. front_end/
  7. inspector_overlay/
  8. node_modules/
  9. scripts/
  10. test/
  11. third_party/
  12. v8/
  13. .clang-format
  14. .editorconfig
  15. .eslintignore
  16. .eslintrc.js
  17. .git-blame-ignore-revs
  18. .gitattributes
  19. .gitignore
  20. .gn
  21. .mailmap
  22. .npmignore
  23. .npmrc
  24. .style.yapf
  25. .stylelintignore
  26. .stylelintrc.json
  27. AUTHORS
  28. BUILD.gn
  29. codereview.settings
  30. DEPS
  31. LICENSE
  32. OWNERS
  33. package-lock.json
  34. package.json
  35. PRESUBMIT.py
  36. README.md
  37. tsconfig.json
  38. WATCHLISTS
README.md

Chrome DevTools frontend

npm package

The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.

Source code

The frontend is available on chromium.googlesource.com.

Project documentation

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