Add NavigationStateKeepAlive map to StoragePartition

Move the map of PolicyContainerHosts keyed by LocalFrameToken from
PolicyContainerHost to StoragePartition. This changes how
PolicyContainerHosts are accessed. Previously there was a global map of
LocalFrameTokens to PolicyContainerHosts. Now there is a map on
StoragePartition of LocalFrameTokens to NavigationStateKeepAlives, from
which the PolicyContainerHost can be accessed. If there is not a
NavigationStateKeepAlive, the PolicyContainerHost should be accessed
directly from the RenderFrameHost.

This also introduces a source SiteInstance to NavigationStateKeepAlive
to be kept alive. This also implicitly keeps the associated
SiteInstanceGroup alive.

Navigations initiated from a different StoragePartition do not inherit
origins or policies across StoragePartitions, so the PolicyContainerHost
and source SiteInstance will not be leaked across StoragePartition
boundaries (e.g. in <webview> tags).

some NavigationPolicyContainerBuilder unit tests to browser tests
PERFETTO_TESTS=`autoninja -C out/Default perfetto_diff_tests && out/Default/bin/run_perfetto_diff_tests`

Test: Enable NavigationBrowserTest that was added previously, move
Bug: 323753235
Change-Id: I8924a8f75831e3b3da2922024349632fe057bfe6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5311170
Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Commit-Queue: Sharon Yang <yangsharon@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1291412}
23 files changed
tree: 18961a89d1ad52f476f83d6312b0cdb9e95d51d0
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. webkit/
  51. .clang-format
  52. .clang-tidy
  53. .clangd
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitallowed
  57. .gitattributes
  58. .gitignore
  59. .gitmodules
  60. .gn
  61. .mailmap
  62. .rustfmt.toml
  63. .vpython3
  64. .yapfignore
  65. ATL_OWNERS
  66. AUTHORS
  67. BUILD.gn
  68. CODE_OF_CONDUCT.md
  69. codereview.settings
  70. CPPLINT.cfg
  71. DEPS
  72. DIR_METADATA
  73. LICENSE
  74. LICENSE.chromium_os
  75. OWNERS
  76. PRESUBMIT.py
  77. PRESUBMIT_test.py
  78. PRESUBMIT_test_mocks.py
  79. README.md
  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.