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

Hi @domfarolino - Some notes from our TAG breakout today:  We're noting that we had previously reviewed an earlier version of this spec and given it a positive review. In fact, we had also specifically called it out as a positive development in our finding on [Improving the Web Without Third Party Cookies](https://www.w3.org/2001/tag/doc/web-without-3p-cookies/#use-cases-previously-met-by-third-party-cookies).
  
We noticed that the changes to this API include Shared Storage as a dependency. Please note that not only does this not have multi-stakeholder support, but important stakeholders have actively expressed opposition to it: e.g. see the [Webkit Standards Position comment](https://github.com/WebKit/standards-positions/issues/173#issuecomment-1584609387), by @annevk and the [Mozilla Standards Position](https://github.com/mozilla/standards-positions/issues/646#issuecomment-1238792961). We've also noted this as an issue in [our ongoing review](https://github.com/w3ctag/design-reviews/issues/747) of Shared Storage. Can you please clarify – is there a dependency on Shared Storage? Does this dependency improve user experience or developer experience of this feature? What's your plan in the (very likely) case that Shared Storage is not implemented by other browsers?

We are actually [working on a design principle](https://github.com/w3ctag/design-principles/issues/11#issuecomment-1515585583) that would state config objects should also accept plain object literals whenever possible. Would that guidance be helpful in your design process?
  
We appreciate the thorough job done on documenting this API. Looking through the [use cases](https://github.com/WICG/fenced-frame/blob/master/explainer/use_cases.md) though, we're struggling to find the user need. We're noting the goal articulated in the [main explainer](https://github.com/WICG/fenced-frame/blob/master/explainer/README.md#goals) but what's missing is a simple articulation of what benefit the user derives from the inclusion of this API in the platform - from the web user's point of view.  We'd also like to see an explanation and code example of how the API is used in its most simple form.

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

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