Google Git
Sign in
chromium / chromium / src.git / dbce6e3f193166cbf93b3fa618c4ccdba284ee76
commitdbce6e3f193166cbf93b3fa618c4ccdba284ee76[log] [tgz]
authorNan Lin <[email protected]>Wed May 10 22:42:55 2023
committerChromium LUCI CQ <[email protected]>Wed May 10 22:42:55 2023
tree09cb5a473d20137ec71f3a8873b7e4cf4f7aeccd
parent306ab77eedb795180903b22d500cc46da86ab3e6 [diff]
Plumb cross app web runtime feature status to browser process

This is a follow up for https://crrev.com/c/4512697.

This CL plumbs cross app web runtime feature status to the browser
process via mojo pipes for Attribution Reporting surfaces that operate
in the browser process: navigations and fenced frame ad beacons. All
other surfaces are handled in Blink in a previous CL.

The runtime features status is then passed to the network service so
that the Attribution-Reporting-Support header is only set when cross app
web is runtime enabled. We may consider replacing this pipeline with
runtime feature state to read the states from the browser process later
on (https://crbug.com/1443561).

The OS source registration from navigation redirects and fenced frame
beacons are only handled if cross app web is runtime enabled as well.

Bug: 1442871
Change-Id: I9398c683a04c519bc495f8aeb3407b0c4e129867
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4507597
Reviewed-by: Andrew Paseltiner <[email protected]>
Commit-Queue: Nan Lin <[email protected]>
Reviewed-by: Charlie Harrison <[email protected]>
Reviewed-by: Garrett Tanzer <[email protected]>
Reviewed-by: Nate Chapin <[email protected]>
Reviewed-by: Joe Mason <[email protected]>
Reviewed-by: Alex Moshchuk <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1142433}
32 files changed
tree: 09cb5a473d20137ec71f3a8873b7e4cf4f7aeccd
  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. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. 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.