← Back to release summary

Partitioning Storage, Service Workers, and Communication APIs

Category
Offline / Storage
Type
New or changed feature
Status
Enabled by default (Chrome 115)
Intent stage
Evaluate readiness to ship

Summary

Note: this has launched in Chrome 115 We intend to partition a number of APIs in 3rd party contexts. This effort is focused on partitioning APIs above the network stack. This includes quota-managed storage, service workers, and communication APIs (like BroadcastChannel). See the explainer for more details: https://github.com/wanderview/quota-storage-partitioning/blob/main/explainer.md There is also a deprecation trial available as well as an enterprise policy: https://developer.chrome.com/blog/storage-partitioning-deprecation-trial/ https://chromeenterprise.google/policies/#DefaultThirdPartyStoragePartitioningSetting

Motivation

Partitioning is intended to address known, existing privacy and security issues in 3rd party contexts. See: https://github.com/privacycg/storage-partitioning#introduction

Standards & signals

Explainers: https://github.com/wanderview/quota-storage-partitioning/blob/main/explainer.md

View on chromestatus.com