Clarify that headers can be used to send beacons without data #1014
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dmdabbs
reviewed
Feb 6, 2024
clementsimon
reviewed
Feb 8, 2024
|
This PR clarifies behaviors discussed here: #826 (comment) #808 (comment) |
github-actions bot
added a commit
that referenced
this pull request
Apr 9, 2024
SHA: 6ab755c Reason: push, by JensenPaul Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Automatic beacons can be sent from an ad frame (without data) without invoking
setReportEventDataForAutomaticBeacons()if the ad frame's page is served with the response headerAllow-Fenced-Frame-Automatic-Beacons: true. We already mention that this is possible for component ads. This PR clarifies that this is also possible for main ad frames.