Re: [w3ctag/design-reviews] Review request for Fenced Frames (Issue #735)

Thanks for the feedback and questions!

> From our initial review we think this looks great from a privacy perspective.
> 
> Regarding the use cases that Fenced Frames are meeting - how are they currently achieved? What will motivate developers to move to Fenced Frames instead?

The use cases that are motivating fenced frames require some kind of cross-site data access. Currently that is available in iframes as third-party cookies. But once 3p cookies are blocked and iframes only access data partitioned by top-level site, cross-site data can only be allowed if the documents that contain data from different partitions are isolated from each other. Iframes do not suit this purpose since they have several communication channels with their embedding frame (e.g., postMessage, URLs, size attribute, etc.). Fenced frames provide such a construct where the fenced frame document and the embedding document are visually composed on the page, but unable to communicate with each other. 

As a specific example, one of the first use cases that fenced frames will solve is interest based advertising. More details of the use case's privacy guarantees are [here](https://github.com/WICG/turtledove#turtledove) . One of the guarantees mentioned there is "Web sites the person visits, and the ad networks those sites use, cannot learn about their visitors' ad interests." and this will be achieved by rendering the auction winning ad in a fenced frame as described [here](https://github.com/WICG/fenced-frame/blob/master/explainer/opaque_ads_use_cases.md#interest-group-ads-based-on-user-activity-turtledove).

> 
> We see you expect to move this work to WHATWG - are there positive signals from other implementers in the WHATWG community? Because right now that is not reflected in Chromestatus.

We plan to reach out to WHATWG more formally in the coming weeks and get signals. /cc @domfarolino 
We have had some initial conversations with other browsers and there has been positive signal from Microsoft Edge ([comment](https://github.com/WICG/proposals/issues/52#issuecomment-1063481655))



-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/735#issuecomment-1155089986
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/735/1155089986@github.com>