commit | 137afa34ab2746d329837eda9189b4140ce47203 | [log] [tgz] |
---|---|---|
author | Matt Menke <mmenke@chromium.org> | Tue Mar 25 15:58:25 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 25 15:58:25 2025 |
tree | d7922e21801c7737184145f947195a3d47dc4f57 | |
parent | 990f09eeffe3e28db63a4714e6de83170bb778d1 [diff] |
Make DeclarativeNetRequestBrowserTests cover PA TKVv2 requests. We're adding caching logic to Protected Audiences trusted key value version 2 requests, which use a very different flow from the non-cache path. This CL enhances and renames a pre-existing DeclarativeNetRequestBrowserTest to make sure TKVv2 requests are wired up to extensions. This CL moves privacy_sandbox_coordinator_test_util.h, needed to set up a coordinator to enable these fetches, to content/public/test/, and makes InterestGroupManagerImpl::AddTrustedServerKeysDebugOverride() a member of InterestGroupManager. It splits DeclarativeNetRequestBrowserTest.FledgeAuctionScripts in two, since leaving it as a single test resulted in unexpected failures that seem unrelated to the changes to the test - an extension seems to have stopped redirecting requests not modified by this CL for some reason. The test was not flaky before, but flaked twice on Android before being split up. Bug: 330322161 Change-Id: If3fd113cce8ed6ef7dae7853312cb8f3a5be3d43 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6330419 Reviewed-by: Dave Tapuska <dtapuska@chromium.org> Reviewed-by: Kelvin Jiang <kelvinjiang@chromium.org> Commit-Queue: mmenke <mmenke@chromium.org> Reviewed-by: Russ Hamilton <behamilton@google.com> Reviewed-by: Kevin Graney <kmg@google.com> Cr-Commit-Position: refs/heads/main@{#1437524}
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.