how long we can rely on the Chrome flag (chrome://flags/#third-party-storage-partitioning)

[michweiss88]

Our product relies on shared local storage functionality, which is deprecated. We've explored alternatives to address this limitation and currently, the solution to overcome it is by disabling the feature in Chrome flags (chrome://flags/#third-party-storage-partitioning). As this functionality is crucial for us, I'm interested in knowing how long can we rely on the Chrome flag workaround?

[miketaylr]

The flag is currently scheduled to be removed in Chrome 129 - see https://issues.chromium.org/u/1/issues/346617041. 129 is currently scheduled to be released in mid-September (see https://chromiumdash.appspot.com/schedule).

I would recommend exploring requestStorageAccess for non-cookie storage:

https://chromestatus.com/feature/5175585823522816
https://developers.google.com/privacy-sandbox/blog/saa-non-cookie-storage (this API shipped in Chrome 125 - it's an older blog post that was posted while the idea was experimental but gives some usage examples).