- From: Anusha Muley <notifications@github.com>
- Date: Tue, 29 Apr 2025 07:00:09 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 29 April 2025 14:00:15 UTC
aamuley left a comment (w3ctag/design-reviews#906) Hey @torgo just wanted to follow up on this since it has been a while, is there any feedback on the explainer extensions @arichiv shared above? I believe the self-review should be very similar to the non-cookie SAA one above but I can also make an entirely new issue if that would be preferable. Was specifically hoping for feedback on the Shared Workers extension! > [Explainer: Extending Storage Access API (SAA) to Shared Workers](https://privacycg.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. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/906#issuecomment-2839041021 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/906/2839041021@github.com>
Received on Tuesday, 29 April 2025 14:00:15 UTC