Google Git
Sign in
chromium/devtools/devtools-frontend/2fbad1da5d6ec00d0d5217c749e8cd01f9019653
commit
2fbad1da5d6ec00d0d5217c749e8cd01f9019653
[log]
author
Adam Raine <asraine@chromium.org>
Wed May 15 19:29:44 2024
committer
Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>
Wed May 15 19:59:24 2024
tree
b781e084ed88ee5d066e758afb6f02175b97afe0
parent
902bb6d6ada919f1ab16404a0539b8bb9bbd460d [diff]
[RenderBlocking] Only consider body requests that are high priority

The render blocking audit in Lighthouse actually has a second level of
filtering that only includes requests that are in the FCP simulation
graph. The FCP simulation graph filters out low priority requests:
http://shortn/_rUloOEiNu9

For requests marked `in_body_parser_blocking` we should ensure that
the priority is high enough to be considered render blocking. There are
exceptions to the logic added but this is the definition Lighthouse has
been using so this is at least a good place to start.

This CL changes nothing about the behavior of requests marked `blocking`

Bug: 328489888
Change-Id: I7700118e78f9f36f62ba5acfb2da68928ccc1879
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5537846
Reviewed-by: Paul Irish <paulirish@chromium.org>
Commit-Queue: Adam Raine <asraine@chromium.org>
6 files changed
tree: b781e084ed88ee5d066e758afb6f02175b97afe0
  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