[blink-dev] Intent to Experiment: Extending Storage Access API (SAA) to non-cookie storage

Contact emails aric...@chromium.org, wanderv...@chromium.org, johann...@chromium.org, hele...@google.com Specification https://arichiv.github.io/saa-non-cookie-storage/ Feedback https://github.com/arichiv/saa-non-cookie-storage/issues Intent to Prototype https://groups.google.com/a/chromi

Re: [blink-dev] Intent to Experiment: Extending Storage Access API (SAA) to non-cookie storage

Can you please also fill out the *Goals for experimentation* section? On Thu, Oct 26, 2023 at 8:21 AM Ari Chivukula wrote: > Contact emails > > aric...@chromium.org, wanderv...@chromium.org, johann...@chromium.org, > hele...@google.com > > > Specification > > https://arichiv.github.io/saa-non-co

Re: [blink-dev] Intent to Experiment: Extending Storage Access API (SAA) to non-cookie storage

Done. ~ Ari Chivukula (Their/There/They're) On Fri, Oct 27, 2023 at 5:25 PM Chris Harrelson wrote: > Can you please also fill out the *Goals for experimentation* section? > > On Thu, Oct 26, 2023 at 8:21 AM Ari Chivukula > wrote: > >> Contact emails >> >> aric...@chromium.org, wanderv...@chro

Re: [blink-dev] Intent to Experiment: Extending Storage Access API (SAA) to non-cookie storage

This makes a lot of sense to me. I hate the idea of pushing folks to use cookies just due to SAA. I see the debate about wanting to deprecate the sync storage APIs, but I agree with you that this is not a useful lever in that debate. Instead we should come up with a holistic deprecation strategy.

Re: [blink-dev] Intent to Experiment: Extending Storage Access API (SAA) to non-cookie storage

A blog post on how to participate in the OT is here: https://developer.chrome.com/blog/saa-non-cookie-storage/ Chrome 120 includes local storage, session storage, indexed db, and web locks. Chrome 121 adds cache storage, origin private filesystem, quota, blob storage, and broadcast channel. Shar

Re: [blink-dev] Intent to Experiment: Extending Storage Access API (SAA) to non-cookie storage

Based on a report from an external developer a bug was found that caused the session/local storage on the SAA handle to sometimes be partitioned (instead of unpartitioned). The fix

Re: [blink-dev] Intent to Experiment: Extending Storage Access API (SAA) to non-cookie storage

Two additional explainers (each of which is an extension to Storage Access API (SAA) to non-cookie storage ) have been published! Both of these are slated for inclusion in the existing origin trial (hopefully as part of M123). Explainer: Extending

Re: [blink-dev] Intent to Experiment: Extending Storage Access API (SAA) to non-cookie storage

Please note the repo has been moved into PrivacyCG, and the new links are: Explainer: Extending Storage Access API (SAA) to non-cookie storage Explainer: Extending Storage Access API (SAA) to omit unpartitioned cookies

Re: [blink-dev] Intent to Experiment: Extending Storage Access API (SAA) to non-cookie storage

Chrome 123 is adding Shared Worker support to the SAA extension. A blog post on how to participate in the OT is here: https://developer.chrome.com/blog/saa-non-cookie-storage/ ~ Ari Chivukula (Their/There/They're) On Mon, Jan 29, 2024 at 1:41 PM Ari Chivukula wrote: > Please note the repo has