[Privacy Sandbox] Support enrollment overrides in chrome://flags
3rd party developers will need to test how their sites behave with
Privacy Sandbox APIs. However, sites are only allowed to use the APIs if
they have been enrolled/have agreed to the Privacy Sandbox attestations.
In order to unblock the developers if their site hasn't been enrolled,
this CL will let them to set a list of origins in their Chromium
instance that can use APIs (such as FLEDGE and Shared Storage) without
needing to check for enrollment.
Note that this approach is temporary. The long-term goal is to integrate
this feature into an upcoming Privacy Sandbox devtools extension. Until
the details of the extension integration have been hashed out, we are
implementing this using a flag.
Change-Id: If742873024c9ea2e450ac6ca827bf07de1a5fd92
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4638542
Reviewed-by: Garrett Tanzer <[email protected]>
Commit-Queue: Liam Brady <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1161847}
diff --git a/chrome/browser/flag_descriptions.cc b/chrome/browser/flag_descriptions.cc
index c7de52f..5f574dc6 100644
--- a/chrome/browser/flag_descriptions.cc
+++ b/chrome/browser/flag_descriptions.cc
@@ -2799,6 +2799,13 @@
"Fenced Frames, Shared Storage, Private Aggregation, and their associated "
"features.";
+const char kPrivacySandboxEnrollmentOverridesName[] =
+ "Privacy Sandbox Enrollment Overrides";
+const char kPrivacySandboxEnrollmentOverridesDescription[] =
+ "Allows a list of sites to use Privacy Sandbox features without them being "
+ "enrolled and attested into the Privacy Sandbox experiment. See: "
+ "https://developer.chrome.com/en/docs/privacy-sandbox/enroll/";
+
const char kPrivacySandboxSettings4Name[] = "Privacy Sandbox Settings V4";
const char kPrivacySandboxSettings4Description[] =
"Enables updated Privacy Sandbox UI";
