Hi Webkit-Dev Team,
We've been working on the Shared Storage API that supports a variety of use
cases that may be impacted by 3rd Party Cookie Deprecation. The idea is to
provide a storage API (named Shared Storage) that is intended to be
unpartitioned. Origins can write to it from their own contexts on any page.
To prevent cross-site tracking of users, data in Shared Storage may only be
read in a restricted environment that has carefully constructed output
gates. Over time, we hope to design and add additional gates.
We would like to hear what you think about it. Chrome is implementing
(available in Chrome Canary on M104) but open to evolving the API over time
and are appreciative of your feedback.
explainer: <https://github.com/jkarlin/topics>
https://github.com/pythagoraskitty/shared-storage/
chromestatus: <https://chromestatus.com/feature/5680923054964736>
https://chromestatus.com/feature/6256348582903808
spec: TBD
Thank you,
Eric
Greetings webkit-dev,
I am requesting your feedback about exposing:
```js
self.crossOriginEmbedderPolicy;
```
It reflects the environment's crossOriginEmbedderPolicy's value.
More details on:
https://github.com/ArthurSonzogni/coep-reflection
Thanks
Arthur @arthursonzogni