Route actor tool calls to correct frame

The CL implements basic routing of BrowserAction requests to the frame
indicated by the ActionTarget's DocumentIdentifier.

This identifier corresponds to a serialized UnguessableToken[1] stored
as UserData on each RenderFrameHost from which an AnnotatedPageContent
is extracted. A mapping of this serialized token back to RenderFrameHost
is provided in the AIPageContentResult[2] but in the Glic context this
is plumbed directly into a callback using the Glic mojo API[3] which
this map shouldn't be stashed into.

Given that we currently always act on the foreground tab (and the
BrowserAction proto will eventually set the tab/task id), it seems low
cost to iterate through the focused tab's RenderFrameHosts looking for
the correct one. Eventually we'll probably want to extract this map
from the context fetcher.

[1] https://source.chromium.org/chromium/chromium/src/+/main:components/optimization_guide/content/browser/page_content_proto_provider.h;l=33;drc=46a97274045543958f5ff7fb0595bed79d265100
[2] https://source.chromium.org/chromium/chromium/src/+/main:components/optimization_guide/content/browser/page_content_proto_provider.h;l=64;drc=1f9f3d7d4227fc2021915926b0e9f934cd610201
[3] https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/glic/host/context/glic_page_context_fetcher.cc;l=310;drc=1f9f3d7d4227fc2021915926b0e9f934cd610201

Bug: 419037299
Change-Id: Id6ce81462a54225e9b97b1892cea2f9d092ffc13
Cq-Include-Trybots: luci.chromium.try:linux-bfcache-rel
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6579529
Reviewed-by: Kevin McNee <mcnee@chromium.org>
Commit-Queue: David Bokan <bokan@chromium.org>
Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1465711}
6 files changed
tree: a46dcb92aa57ecbea83b98310b28c70a29b67744
  1. .github/
  2. android_webview/
  3. apps/
  4. ash/
  5. base/
  6. build/
  7. build_overrides/
  8. buildtools/
  9. cc/
  10. chrome/
  11. chromecast/
  12. chromeos/
  13. codelabs/
  14. components/
  15. content/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. gpu/
  25. headless/
  26. infra/
  27. ios/
  28. ipc/
  29. media/
  30. mojo/
  31. native_client_sdk/
  32. net/
  33. pdf/
  34. ppapi/
  35. printing/
  36. remoting/
  37. rlz/
  38. sandbox/
  39. services/
  40. skia/
  41. sql/
  42. storage/
  43. styleguide/
  44. testing/
  45. third_party/
  46. tools/
  47. ui/
  48. url/
  49. webkit/
  50. .clang-format
  51. .clang-tidy
  52. .clangd
  53. .git-blame-ignore-revs
  54. .gitallowed
  55. .gitattributes
  56. .gitignore
  57. .gitmodules
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython3
  62. .yapfignore
  63. ATL_OWNERS
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. CPPLINT.cfg
  69. CRYPTO_OWNERS
  70. DEPS
  71. DIR_METADATA
  72. LICENSE
  73. LICENSE.chromium_os
  74. OWNERS
  75. PRESUBMIT.py
  76. PRESUBMIT_test.py
  77. PRESUBMIT_test_mocks.py
  78. README.md
  79. SECURITY_OWNERS
  80. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure.

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.