As of 9 May 2022, I intend to ship a feature that causes Storage to be partitioned, even when the Storage Access API is used. This proposed behavior is currently implemented and used by Safari and Blink. Chrome does not support storage partitioning, so this behavior is not defined.
Tracking Bug: Bug 1758737 - [meta] Always Partition Storage <https://bugzilla.mozilla.org/show_bug.cgi?id=1758737> Initially the Storage Access API was designed as an authenticated backdoor to allow unpartitioning different types of storage that are being partitioned, e.g. to prevent cross-site tracking. The scope of effect of the Storage Access API was not precisely defined and it is an open issue in the draft specification if it should apply to Storage and Cookies or just Cookies: https://privacycg.github.io/storage-access/#storage . We would like to prototype the change that would bring us in line with the other implementations of the Storage Access API. This has no change in user privacy impact and has minor risk for breakage in an experimental API. Related discussion: https://github.com/privacycg/storage-partitioning/issues/4 -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CAJCrZTdXZmQrhJPQKukUZA1VJqLH6VqQ%2BjHyKuvS8LFNVNPRuA%40mail.gmail.com.
