Re: [w3ctag/design-reviews] Specification review for fenced frames (Issue #838)

> 
> To add to above, fenced frames do not have a dependency on Protected Audience and are a generic element providing stronger isolation between the embedder and the frame, such that they are visually composed on the same page but cannot join cross-site identifiers. As the [TAG had requested above](https://github.com/w3ctag/design-reviews/issues/838#issuecomment-1892661808), the updated use cases document is now published [here](https://github.com/WICG/fenced-frame/blob/master/explainer/use_cases.md). As an example of non-Protected Audience use case that fenced frames intend to support, as mentioned in the [earlier comment](https://github.com/w3ctag/design-reviews/issues/838#issuecomment-1667970369), we are in the process of adding functionality for local unpartitioned data access which will support use cases like personalized payment buttons. That functionality is described in this [explainer](https://github.com/WICG/fenced-frame/blob/master/explainer/fenced_frames_with_local_unpartitioned_data_access.md) and the spec is currently in progress. Since this is a major update, we are happy to open a new TAG request specifically for this when the spec is more ready, or add to this request, as the TAG reviewers may see fit.

I went ahead and created an early design TAG review for this new functionality: https://github.com/w3ctag/design-reviews/issues/975

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

Message ID: <w3ctag/design-reviews/issues/838/2221314377@github.com>