demo · v132

Debug Mode Comparison

Chrome 132 fixes an edge case: previously, a caller could enable Private Aggregation debug mode if they could set a third-party cookie — even if the user had globally blocked 3P cookies and the site was only allowed via a per-site exception. Chrome 132 ignores per-site exceptions when evaluating debug-mode eligibility. Toggle the combinations below to see exactly when debug mode fires pre-132 vs Chrome 132.

Cookie and enrollment configuration

User has NOT blocked all 3P cookies in settings
User added an exception for this site specifically
Pre-Chrome 132 — debug mode eligibility
Chrome 132 — debug mode eligibility
// Chrome 132: Private Aggregation debug mode eligibility
// The key change: site-level exceptions are IGNORED.
// Only the user's GLOBAL 3P cookie setting matters for debug mode.

// worklet.js
privateAggregation.enableDebugMode({ debugKey: 123n });
privateAggregation.contributeToHistogram({ bucket: 1n, value: 10 });

// Pre-132 eligibility check (simplified):
// canUseDebugMode = isEnrolled && canSetThirdPartyCookie(caller)
//                  // canSetThirdPartyCookie was TRUE for site exceptions too

// Chrome 132 eligibility check:
// canUseDebugMode = isEnrolled
//                  && globalThirdPartyCookiesAllowed()
//                  // site exceptions are IGNORED
//                  // debug mode requires global cookies, not site exceptions

see also