v152 · removal · privacy sandbox

Deprecate and Remove: document.requestStorageAccessFor

The requestStorageAccessFor entry point — Chrome's mechanism for top-level sites to request unpartitioned cookie access on behalf of embedded sites — is being deprecated alongside Related Website Sets. In the absence of broad third-party cookie deprecation, this API no longer has a job to do.

concepts

  1. Call Status

    Attempts a real call to document.requestStorageAccessFor(origin) and reports what came back — granted, denied, or undefined. Useful for tracking the deprecation timeline across Chrome releases.

  2. Migration Lab

    Side-by-side: the legacy top-level requestStorageAccessFor call vs. the recommended replacement — requestStorageAccess() invoked from inside an embedded iframe.

  3. API Surface Probe

    Live check of all three Storage Access API methods — hasStorageAccess(), requestStorageAccess(), and requestStorageAccessFor() — showing which are present and which are removed in Chrome 152.

  4. Storage Access Migration Guide

    A step-by-step wizard identifying your use case (3P cookies, Storage Access API, CHIPS, RWS), showing old vs. new code for each, with live tests of the removed requestStorageAccessFor() versus its replacements, plus a full deprecation timeline.

  5. Partition Visualizer

    Toggle between the Chrome 152+ partitioned storage model and the pre-150 requestStorageAccessFor model. Visual storage buckets show how the same embedded origin gets isolated partition keys per top-level site under the new model, versus the unpartitioned cross-site sharing that was possible before.

  6. Cookies Fallback Test

    Probes all three Storage Access API methods — hasStorageAccess(), requestStorageAccess(), and the removed requestStorageAccessFor() — and reports their presence in your current browser. Shows the correct replacement pattern (calling requestStorageAccess() from inside an embedded iframe after a user gesture) versus the top-level call that was removed.

    Live probe Storage Access API Migration

why it shipped

This API was designed for the world that was about to exist: third-party cookies gone, RWS as the surviving cross-origin bridge, and requestStorageAccessFor as the front door. Now that that world isn't coming, the API is dead weight. The deprecation is paired with the broader RWS removal so the entire stack winds down together.

references