4 ms·
The recommended solution for embedded content is the Storage Access API, which has broad browser support. (I don't know that YouTube has implemented it yet, but
by medmunds 2y ago
The recommended solution for embedded content is the Storage Access API, which has broad browser support. (I don't know that YouTube has implemented it yet, but I'd be surprised if it's not there soon.)
https://developer.mozilla.org/en-US/docs/Web/API/Storage_Access_API https://developer.mozilla.org/en-US/docs/Web/API/Storage_Acc...
https://developers.google.com/privacy-sandbox/3pcd/storage-access-api https://developers.google.com/privacy-sandbox/3pcd/storage-a...
- lordofmoria 2y agoThe Storage Access API is an unmitigated pile of garbage. Google's page on it admits as much (https://developers.google.com/privacy-sandbox/3pcd/storage-access-api https://developers.google.com/privacy-sandbox/3pcd/storage-a...). From Google's own page: "Work is continuing to resolve all remaining blocking issues, before standardizing the API."
- medmunds 2y agoOh, that's worrisome. I'm trying to implement it in our embedded content soon, because some of our customers got caught up in Chrome's third party cookie blocking 1% trial that started a week or two ago. Any specific problems you ran into that you could share?