[wpt-sync] Sync PR 46611 - Fenced frame: Set referrer header for all event-level beacons.
Categories
(Core :: DOM: Core & HTML, task, P4)
Tracking
()
Tracking | Status | |
---|---|---|
firefox129 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Attachments
(1 file)
383.78 KB,
text/plain
|
Details |
Sync web-platform-tests PR 46611 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/46611
Details from upstream follow.
Liam Brady <lbrady@google.com> wrote:
Fenced frame: Set referrer header for all event-level beacons.
A previous CL set the "Referer" header for reportEvent() beacons to the
frame's origin. This CL sets that header for automatic beacons as well,
and puts the change behind a new feature flag. Automatic beacons from
component ads will not have their "Referer" header set to the frames
origin for privacy reasons, and instead will be set to the root ad
frame's origin. To track this, ad component configs will now store the
origin of the root ad frame's config on the browser side.This CL also updates WPTs and other tests to account for the changes.
Previous CL:
https://chromium-review.googlesource.com/c/chromium/src/+/5551871Design Doc:
https://docs.google.com/document/d/1gKRZ9g_X5HCZbW__GinViwcC8iWEai_kBXsiJCXrt80/edit?usp=sharingChange-Id: Idfaeee92ad5bf471b34002a6a701290d1ae31cf1
Bug: 341884774
Reviewed-on: https://chromium-review.googlesource.com/5544804
WPT-Export-Revision: 54de6cb0a9515e0041431b323ec4ba5af5245f20
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 1•1 year ago
|
||
Assignee | ||
Comment 2•1 year ago
|
||
Comment 4•1 year ago
|
||
bugherder |
Description
•