Privacy Sandbox compatibility
adamziel opened this issue · 4 comments
adamziel commented
Privacy Sandbox and the deprecation of third-party cookies is right around the corner. Let's make sure the Playground <iframe> keeps working as these changes are rolled out.
Related:
Noteworthy:
- The disable third-party cookies option in Chrome is not a good reflection of how Chrome is going to when when the third-party cookies deprecation becomes the default. Some things are still in flux.
- Storage Partitioning for service workers. My understanding is that Partitioned Service Workers should just work without any changes in Playground
- Origin trials make it possible to enable some of these experimental new features on specific sites, like playground.wordpress.net. I wanted to sign up for the storage, but they aren’t active trials at the moment unfortunately.
- Chromestatus.com has a searchable database of all Chrome features and upcoming APIs – super valuable stuff.
- https://github.com/privacycg/storage-access
- Extending Storage Access API (SAA) to non-cookie storage
cc @dmsnell
arichiv commented
Wanted to note that Chrome is working on extending the Storage Access API (aiming to ship in Chrome soon) with support for access to first-party storage for a given origin from a third-party context for that same origin. This would require you to call requestStorageAccess() (which would show a user permission prompt).
More details here: privacycg/storage-access#102
adamziel commented
This one could potentially be already addressed and needs re-assessing.