- From: Shivani Sharma <notifications@github.com>
- Date: Fri, 03 Feb 2023 08:57:51 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 3 February 2023 16:58:04 UTC
> For what’s worth, I’d also be interested to learn about the risks of fenced frames prior to the removal ot third-party cookies. One risk I can imagine is the false sense of isolastion — that the developer/user may think that something is tight, but it maybe isn’t. Is that the raised problem here? @lknik agree that there are existing leaks in FFs, some of them mentioned in the explainer [here](https://github.com/WICG/fenced-frame/tree/master/explainer#ongoing-technical-constraints). To the user, FFs currently do not show any UX difference and since they are strictly better than iframes with 3pc, I think that would be ok. To developers, we could likely clarify the existing documentation enumerating the existing leaks. Would that help? -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/735#issuecomment-1416141199 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/735/1416141199@github.com>
Received on Friday, 3 February 2023 16:58:04 UTC