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.

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

Explainer update for cross-origin automatic beacon data support. #1386

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

blu25
Copy link
Contributor

@blu25 blu25 commented Jan 17, 2025

Documents that are cross-origin to an ad frame root can now set data to be used with automatic beacons with proper opt-ins. Update the FFAR explainer document to reflect those changes.

To opt in the data, the dictionary passed into `setReportEventDataForAutomaticBeacons` takes an optional `crossOriginExposed` boolean that defaults to false. If set to true, the automatic beacon data can be used if a cross-origin document wants to send an automatic beacon and is opted in. A document will use the data of the first ancestor frame that has automatic beacon data registered for the event type being sent.
A cross-origin document opts in by being served with the response header `Allow-Fenced-Frame-Automatic-Beacons: true`.

To use data for cross-origin automatic beacons, the dictionary passed into `setReportEventDataForAutomaticBeacons` takes an optional `crossOriginExposed` boolean that defaults to false. If set to true, the automatic beacon data can be used if a cross-origin document wants to send an automatic beacon and is opted in. A document will use the data of the first ancestor frame that has automatic beacon data registered for the event type being sent.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this statement isn't too clear on who needs to call the setReportEventDataForAutomaticBeacons() with crossOriginExposed set to true: is it the ancestor or the cross-origin iframe itself can do that. Let's clarify.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants