-
Notifications
You must be signed in to change notification settings - Fork 696
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
Will this allow sending Cross-Domain messages? #159
Comments
RWS integrates with the Storage Access API so the improvements being made as part of privacycg/storage-access#102 will benefit developers using RWS as well, there's no relaxation of cross-site storage / communication APIs from RWS otherwise.
The full steps are at https://github.com/GoogleChrome/related-website-sets/blob/main/Getting-Started.md, you should edit the main related_website_sets.JSON file in your PR. |
@jcubic Note that we are currently running an Origin Trial between Chrome 120-124 if you'd like to test out the use of Storage Access API (SAA) to re-gain access to cross-site communication via localStorage or Broadcast Channel; please see details here. If the sites in question are within the same RWS, your SAA invocation will be auto-granted in Chrome. cc @arichiv |
@krgovind I already did a month ago. |
Ah, indeed. I missed the fact that you had provided feedback on the relevant repo. Thank you! |
In one of the recent version of Chrome new feature was added storage partitioning, that don't allow cross-domian communication on not related domains (it only works for subdomains).
Found this repo in Storage Access API article on MDN. Link from a new article Saying goodbye to third-party cookies in 2024
Will this API allow sending Cross Domain messages (with localStorage storage event or Broadcast channel)?
Also, it's not clear how to submit the set. Should I create a PR for this repo and add a JSON file? If yes then it's not clear where to add those JSON files.
I need this for my Open Source project that stopped working in Chrome for not related domains jcubic/sysend.js#54
The text was updated successfully, but these errors were encountered: