Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cross-tab communication via events #107

Open
elimenko opened this issue Aug 24, 2023 · 3 comments
Open

Cross-tab communication via events #107

elimenko opened this issue Aug 24, 2023 · 3 comments

Comments

@elimenko
Copy link

So recently our team got hit by the Storage Partitioning flag rollout in the latest Chrome versions, which broke our mechanism of cross tab communication via Local Storage events.
We have a setup where site a.example.com embeds an iframe from site b.example.com. We have a mechanism where user action on site a.example.com opens a new browser tab in the b.example.com domain. Previously we were relying on Local Storage events for communication between those two tabs, but now, due to storage partitioning, it's no longer possible.
It seems that Shared Storage is designed to have secured cross-site unpartitioned storage, but searching through documentation I haven't found if we are able to use some like Storage Events with Shared Storage. Does it sound like Shared Storage is capable of helping in my case? Thanks in advance!

@xyaoinum
Copy link
Collaborator

Shared storage has carefully constructed output gates. The "Window: storage event" API as is can leak arbitrary amount of information, which doesn't seem to be something Shared Storage can support.

@elimenko
Copy link
Author

@xyaoinum Thank you for the answer. May be you could suggest, which approach can be used for cross-tab cross-domain communication in the Privacy Sandbox? It seems that for Cookies we can rely on First Party Sets. Is there anything similar to this, but for other storage types?

@menonasha
Copy link

@elimenko I believe this thread is the most relevant to your ask and it may be worth posting more about your use case there

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants