Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Explain credentials on automatic beacons until 3PCD #884

Merged
merged 3 commits into from
Nov 9, 2023
Merged

Explain credentials on automatic beacons until 3PCD #884

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ac6afc0
Add description of credentials on automatic beacons
gtanzer Oct 25, 2023
d758d75
apply Shivani's edit
JensenPaul Nov 6, 2023
349884f
Merge branch 'main' into patch-4
JensenPaul Nov 9, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 2 additions & 0 deletions Fenced_Frames_Ads_Reporting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -250,6 +250,8 @@ window.fence.setReportEventDataForAutomaticBeacons({
});
```

When 3rd party cookies are enabled, automatic beacon requests only (not beacons sent manually through `reportEvent`) allow credentials (cookies) to be set in headers. This was requested by https://github.com/WICG/turtledove/issues/866 in order to help with migration. These requests are subject to CORS and only occur after opt-in by virtue of calling the `setReportEventDataForAutomaticBeacons` API.
JensenPaul marked this conversation as resolved.
Show resolved Hide resolved

# Support for Ad Components
For ad components [rendered in fenced frames](https://github.com/WICG/turtledove/blob/main/FLEDGE.md#4-browsers-render-the-winning-ad), the support for event-level reporting described below is available in Chrome starting M114.
For ad components rendered in iframes, the support will be available in Chrome starting M115. The support works for all combinations of the top-level ad and ad component being rendered in iframes and/or Fenced Frames.
Expand Down