[go: nahoru, domu]
Google Git
Sign in
chromium / devtools / devtools-frontend / 360463523655b99e55dc720853863f4933a23fae
commit360463523655b99e55dc720853863f4933a23fae[log] [tgz]
authorJack Franklin <jacktfranklin@chromium.org>Mon Feb 27 12:17:37 2023
committerDevtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Feb 27 16:02:58 2023
treef4ee3740aa7e92da4163f56993b9dcb876686dfd
parent1125082cb622e20f9afd8d186d6cd8315f090bbc [diff]
Fix errors on traces with FLEDGE

When looking into the support for OPP for FLEDGE frames (introduced in
crrev.com/c/3686811) I discovered that the new trace engine errors on
them. This is because in the test trace, there seem to be two navigation
events for the same thread but different process ID, which breaks an
assumption we had. I am going to explore this further and chat to people
who can hopefully help clarify the behaviour here, but in the mean time
let's fix it so it does not error.

Bug: none
Change-Id: Ie8a770855d24c9e7d59d4215eaf04dcc1d0cea1a
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4288881
Commit-Queue: Jack Franklin <jacktfranklin@chromium.org>
Reviewed-by: Andres Olivares <andoli@chromium.org>
4 files changed
tree: f4ee3740aa7e92da4163f56993b9dcb876686dfd
  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