search

WICG / fenced-frame

Proposal for a strong boundary between a page and its embedded content
https://wicg.github.io/fenced-frame/
Other
128 stars 32 forks source link

Viewability information for the fenced frame #8

Open shivanigithub opened 3 years ago

shivanigithub commented 3 years ago

Currently iframes are able to observe changes in their intersection with an ancestor element or with a top-level document's viewport via the IntersectionObserver API. Fenced frames cannot observe the IO API because that could be used as a channel of communication between the embedding page and the FF.

But there are dependent use cases e.g. ads require this information for billing, spam detection etc. and we are working towards an alternative to the IO API where the browser provides some new APIs that allow such reporting.

This could be something declarative, similar to the reporting API proposed here or an alternative design.

The design is not finalized at the moment and we are looking to understand design constraints/requirements from consumers like ad tech vendors. Please chime in with your thoughts/inputs for this.

dmdabbs commented 1 year ago

See also https://github.com/WICG/turtledove/issues/264 issue thread in FLEDGE repo regarding Viewability &c.