Implement Storage Access API

[jumde]

whatwg/html#3338

[fmarier]

Microsoft is implementing this and is proposing to upstream it: https://groups.google.com/a/chromium.org/d/topic/blink-dev/e5fu5Q06ntA/discussion

[FYJen]

With Safari and Firefox supporting this feature, is there a timeline on when Brave will support it? Chrome's is in progress - https://bugs.chromium.org/p/chromium/issues/detail?id=989663.

With Brave being the privacy-first browser, this Storage Access API offers additional optionality for the developers to provide fine-grained access control and to explicitly obtain user consent.

[laughinghan]

Brave has previously said "we would use this if it were already implemented in Chromium" whatwg/html#3338 (comment)

[pes10k]

closing in favor of #8514 (Since the API now exists in chromium, and #8514 covers how we'd actually use it)

[drmercer-lucid]

Any updates on actually supporting the Storage Access API - i.e. allowing third-party iframes to request access to their own first-party storage? AFAIK ephemeral storage does not at all solve the problems that SAA was intended to solve 🙃

[JannisBush]

Any updates on actually supporting the Storage Access API - i.e. allowing third-party iframes to request access to their own first-party storage? AFAIK ephemeral storage does not at all solve the problems that SAA was intended to solve 🙃

This blog post from Brave makes it sound like Brave does not plan on ever supporting it: https://brave.com/privacy-updates/24-google-sign-in-permission/

Brave disables the storage access API in Chromium as we believe this approach is not the right way to protect privacy on the Web. The storage access API asks users to make privacy-risking choices they do not understand, and generally requires users to bear the burden of protecting their own privacy.