Limited availability
Experimental: This is an experimental technology
Check the Browser compatibility table carefully before using this in production.
The Fence
interface of the Fenced Frame API contains several functions relevant to <fencedframe>
functionality.
Fence
objects are accessed through the Window.fence
property, but they are only available to documents embedded inside <fencedframe>
s (loaded via FencedFrameConfig
s) or <iframe>
s (loaded via opaque URNs).
Note: See How do <fencedframe>
s work? for some description around FencedFrameConfig
s and opaque URNs.
getNestedConfigs()
Experimental
Returns the FencedFrameConfig
s loaded into <fencedframe>
s embedded inside the current <fencedframe>
.
reportEvent()
Experimental
Triggers the submission of report data via a beacon to one ore more specific URLs registered via the registerAdBeacon()
method of the Protected Audience API, for the purpose of collecting ad auction results.
setReportEventDataForAutomaticBeacons()
Experimental
Specifies event data that will be sent when a navigation occurs inside a <fencedframe>
. This data will be sent via an automatic beacon to one or more specific URLs registered via the registerAdBeacon()
method of the Protected Audience API, for the purpose of collecting reporting data for ad auction results.
window.fence.reportEvent({
eventType: "click",
eventData: JSON.stringify({ clickX: "123", clickY: "456" }),
destination: ["buyer", "seller"],
});
Specifications Browser compatibility See also
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3