[go: nahoru, domu]
Google Git
Sign in
chromium / devtools / devtools-frontend / a93c813ae9e527aea289171f2ad7c43e7ffac98f
commita93c813ae9e527aea289171f2ad7c43e7ffac98f[log] [tgz]
authorAndrés Olivares <andoli@chromium.org>Mon Jul 31 09:17:27 2023
committerDevtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jul 31 10:18:31 2023
tree6639f7cb2200441eb8425a21842cc7afded124ba
parent2d0a199d6b50cc3cb6b8ca6539859045b52fb5e1 [diff]
[RPP] Support  multiple URLs by renderer process

Before this CL, the MetaHandler supported the possibility to assign
multiple processes to each frame. However it was not contemplating the
possibility that a given process might have different URLs. This is an
actual possibility and it is supported by the OPP's model. I noted this
discrepancy after seeing the same track being rendered with different
URLs when appended by the OPP and by the new engine.

This changes the data structure in the MetaHandler that tracks processes
in frames so that multiple windows are tracked for each process, where a
new window is pushed if we detect that the process URL changed. The
RendererHandler is also changed so that the URL assigned to a process
corresponds to the first rendered frame's URL (the process URL is the
one we use in the process' track).

Bug: 1428024
Change-Id: Iac8a3280b41d68144c57be93c17407474cba4750
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4729684
Reviewed-by: Jack Franklin <jacktfranklin@chromium.org>
Commit-Queue: Andres Olivares <andoli@chromium.org>
10 files changed
tree: 6639f7cb2200441eb8425a21842cc7afded124ba
  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. .editorconfig
  16. .eslintignore
  17. .eslintrc.js
  18. .git-blame-ignore-revs
  19. .gitattributes
  20. .gitignore
  21. .gn
  22. .mailmap
  23. .npmignore
  24. .npmrc
  25. .style.yapf
  26. .stylelintignore
  27. .stylelintrc.json
  28. AUTHORS
  29. BUILD.gn
  30. codereview.settings
  31. DEPS
  32. LICENSE
  33. OWNERS
  34. package-lock.json
  35. package.json
  36. PRESUBMIT.py
  37. README.md
  38. tsconfig.json
  39. 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