Re: [w3ctag/design-reviews] Extending Storage Access API (SAA) to non-cookie storage (Issue #906)

Two additional explainers (each of which is an extension to [Storage Access API (SAA) to non-cookie storage](https://arichiv.github.io/saa-non-cookie-storage/)) have been published!

[Explainer: Extending Storage Access API (SAA) to omit unpartitioned cookies](https://arichiv.github.io/saa-non-cookie-storage/omit-unpartitioned-cookies.html)
The current Storage Access API requires that unpartitioned cookie access is granted if any unpartitioned storage access is needed. This forces unpartitioned cookies to be included in network requests which may not need them, having impacts on network performance and security. Before the extension ships, we have a chance to fix this behavior without a compatibility break.

[Explainer: Extending Storage Access API (SAA) to Shared Workers](https://arichiv.github.io/saa-non-cookie-storage/shared-workers.html)
There has been increasing developer and implementer interest in first-party workers being available in third-party contexts the same way that third-party cookies already can be. In the absence of such a solution, we leave developers without a robust way to manage cross-tab state for frames loading the same origin. This explainer proposes a solution for developers to regain third-party access to Shared Workers in select instances to avoid user-facing breakage in browsers shipping storage partitioning.

Would it be possible to get review on this issue of those as well?

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

Message ID: <w3ctag/design-reviews/issues/906/1896609812@github.com>