[go: nahoru, domu]
Google Git
Sign in
chromium / devtools / devtools-frontend / 097b1c7a4edc8530120b2b4b382ae890e799c4e1
commit097b1c7a4edc8530120b2b4b382ae890e799c4e1[log] [tgz]
authorAndrés Olivares <andoli@chromium.org>Wed Apr 05 12:24:52 2023
committerDevtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Apr 05 13:15:46 2023
treeee281e709ce04ff1b4acd839c3c79a72d0375a04
parent33c3f0871ca7d15b2b04eff76633b6038b71fb55 [diff]
[RPP] Use source maps to resolve script location when recording is fresh

As of https://crrev.com/c/4358379 the script location is determined
using its URL only. This was done to prevent script ids from a trace
file being matched with scripts of the inspected target, when the file
and the target are unrelated. However that also meant that we lost the
ability to resolve script files using source maps in cases where this
was possible, for example on fresh recordings.

This CL fixes this issue by checking if the current timeline comes from
a fresh recording. If so, it attemps to resolve the script location as
it did before, else it defaults to using the URL.

Bug: 1430444
Change-Id: I1ee640c51d8604976e92cd7393421622c9d62df9
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4397719
Reviewed-by: Jack Franklin <jacktfranklin@chromium.org>
Commit-Queue: Andres Olivares <andoli@chromium.org>
6 files changed
tree: ee281e709ce04ff1b4acd839c3c79a72d0375a04
  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