Re: [w3ctag/design-reviews] Fenced frames with local unpartitioned data access (Issue #975)

To give some more context on the 3 fenced frames TAG reviews so far:

These 2 that were created where fenced frames support use cases requiring src which should be hidden from the embedder. Examples of these use cases are [Protected Audience](https://github.com/WICG/fenced-frame/blob/master/explainer/use_cases.md#rendering-ads-via-the-protected-audience-api) and [selectURL](https://github.com/WICG/fenced-frame/blob/master/explainer/use_cases.md#selecting-and-rendering-a-url-based-on-cross-site-data-via-selecturl)
- "early design" https://github.com/w3ctag/design-reviews/issues/735 which was resolved positively
- "specification review" https://github.com/w3ctag/design-reviews/issues/838 

And this TAG review that specifically focuses on [local unpartitioned data access rendering](https://github.com/WICG/fenced-frame/blob/master/explainer/use_cases.md#personalizing-document-content-with-local-unpartitioned-data-access)

If it is recommended to instead converge this issue with https://github.com/w3ctag/design-reviews/issues/838 to review all use cases together, we could do that. 

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

Message ID: <w3ctag/design-reviews/issues/975/2334762247@github.com>