Re: [w3ctag/design-reviews] First-Party Sets (#342)

Hi,

@plinss and I took a look at this today in our Wellington F2F. The explainer appears [to identify](https://github.com/krgovind/first-party-sets#applications) only one use case:

> [W]eb platform features can use first-party sets to determine whether embedded content may or may not access its own state[…] It may be reasonable to allow a `https://b.example` iframe within `https://a.example` to access the `https://b.example` databases.

Isn't this solved by the [Storage Access API](https://github.com/privacycg/storage-access)? If it is, we can solve this use case with that API while avoiding the attractive nuisance concern with FPS that @annevk raised. Shouldn't we do that instead?

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