Ari Chivukula
Ari Chivukula
I could use some feedback on https://github.com/whatwg/fetch/pull/1434 @annevk before adding more detail. I know the concept of 'cross-origin request' or 'serialized header size' aren't properly defined.
@yoavweiss would you be willing to review? I think you volunteered to help as a spec mentor :-)
Wanted to give a heads up that the Storage Access API extension OT is adding Shared Worker support in M123: https://developers.google.com/privacy-sandbox/blog/saa-non-cookie-storage
If you're currently using the same domain for the chat iframe on every customer, RWS won't work as you couldn't make a set with every single customer and your own...
We are gathering feedback on this sort of use case but don't have any announcements as of yet on mitigations.
I talked to @cfredric from https://github.com/GoogleChrome/related-website-sets/issues/314 and we had one potential recommendation with many caveats. If we take the example of Customer 1 on https://example.retail/ who has two other sites...
Ah, I think you're right I should have said it bypassed just the prompt.
@dcthetall and I are discussing it and hope to have a proposal of some kind in the first half of this year. We likely won't be able to pursue option...
> 1. Would the proposed solution not require user interaction and user prompt? We are hoping that a prompt would not be required as the data is transient and scoped...
1) We expect to share further updates and details in the near future. 2) While we can't predict what exact user preferences will be, it’s important for businesses and developers...