Ignoring site exceptions for Private Aggregation debug mode availability in M132+
77 views
Skip to first unread message
Alex Turner
Nov 5, 2024, 9:37:02 AM
11/5/24
to shared-storage-a...@chromium.org, fledge-ap...@chromium.org
Hi everyone,
Starting in M132, eligibility for Private Aggregation’s debug mode is changing slightly. After the change, debug mode will now only be available for users who have third-party cookies generally enabled on their browser. That is, if a user has third-party cookies generally disabled, but has put a top-level site on their third-party cookie allowlist, debug mode will still not be available for that site.
This change is being made to protect data that may have been saved from other top-level sites not on the exception list. Note that you do not need to change how you call the API. As before, when debug mode is not available, a call to privateAggregation.enableDebugMode() will be ignored by the browser.
If you have any questions or comments, reply to this post or open an issue in the Privacy Sandbox Dev Support repository on GitHub.
Starting in M132, eligibility for Private Aggregation’s debug mode is changing slightly. After the change, debug mode will now only be available for users who have third-party cookies generally enabled on their browser. That is, if a user has third-party cookies generally disabled, but has put a top-level site on their third-party cookie allowlist, debug mode will still not be available for that site.
This change is being made to protect data that may have been saved from other top-level sites not on the exception list. Note that you do not need to change how you call the API. As before, when debug mode is not available, a call to privateAggregation.enableDebugMode() will be ignored by the browser.
If you have any questions or comments, reply to this post or open an issue in the Privacy Sandbox Dev Support repository on GitHub.
Reply all
Reply to author
Forward
Search
Clear search
Close search
Google apps
Main menu
