← Back to release summary

Fenced frames - Send "Referer" header in beacons

Category
Miscellaneous
Type
No developer-visible change
Status
Enabled by default (Chrome 132)
Intent stage
None

Summary

Reporting beacons (for FenceEvent-built destination enum events, FenceEvent-built automatic beacon events, and macro-substituted destination URL events) will have their "Referer" header set to the initiating frame's origin. This is a strictly additive change, as the "Referer" header is currently unpopulated for all fenced frame event-level reports.

Standards & signals

View on chromestatus.com