*Contact Emails*
[email protected], [email protected], [email protected],
[email protected], [email protected]

*Explainer*
https://github.com/arichiv/opener-storage-partitioning/blob/main/README.md

*Summary*
This proposal seeks to prevent or limit same-origin cross-frame
communication that can bypass storage partitioning
<https://developer.chrome.com/en/docs/privacy-sandbox/storage-partitioning/>,
and to do so in alignment with existing work on the
Cross-Origin-Opener-Policy
<https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Opener-Policy>
.

This will be done in two steps. First, whenever a frame navigates
cross-origin any other windows with a window.opener handle pointing to the
navigating frame will have that handle cleared. Second, any frames with a
valid window.opener (or window.top.opener) handle at the time of navigation
will have transient storage via a StorageKey nonce instead of access to
standard first- and third-party StorageKeys.

Rough target for an origin trial severing window.opener on cross-site
navigation is Q4 2023 while transient storage for frames with a
window.opener likely needs to wait for storage partitioning to fully launch
first.

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGpy5DLTmXFYhFZScCSPcEsUrj9WiN-KAcosf_fOprQPcYy2og%40mail.gmail.com.

Reply via email to