Thanks for sharing.  I have a few questions and concerns about this
approach, which might be worth discussing.

1) Giving transient storage to windows with openers (i.e., Proposal 2)
seems like a reasonable way to prevent a subframe in one partition from
leaking info to a same-origin popup in a primary partition.  It does seem
like it would degrade single-sign-on quite a bit by making users sign into
every new OAuth popup (per your User Friction
<https://github.com/arichiv/opener-storage-partitioning/blob/main/README.md#user-friction>
note), correct?  That may be worth consideration by API owners.

2) I'm guessing that the "clearing the opener" behavior in Proposal 1
mostly exists so that the popup has the ability to leave the transient
storage state?  It does seem safe, but I'm not sure I see a common scenario
where that would happen in practice, without causing unexpected
interactions between tabs.  If A opens B, it seems potentially surprising
for A's window to control whether B's next navigation switches storage
partitions or not.  Is there an example of a flow where this will be
useful, or is Proposal 1 something that could be skipped to reduce the
complexity?

3) I think there may be ways to bypass this approach, since window.opener
is not the only way to get a reference to another window in the same
Browsing Context Group.  For example, you can look up a named window, which
might allow a subframe to find a same-origin document in a primary
partition.  Example:

   -

   On page A(B1), B1 runs window.open(B2, "foo").  B2 is now a named popup
   with an opener and thus transient storage.
   -

   B1 navigates to C, causing B2's opener to be hidden (i.e., "pending").
   -

   B2 navigates to B3, upgrading to primary storage for origin B since it
   has no opener.
   -

   C navigates back to B1.  B3 does not have its opener restored, since B1
   and B3 weren't sharing an opener in the past.  However, both windows are
   still in the same Browsing Context Group.
   -

   B1 does window.open("", "foo"), giving B1 a reference to B3 and creating
   a new window.opener in B3.  This allows B1 (in A's storage partition) to
   synchronously script B3 (in B's primary storage partition).

Would you need to block named window lookup across storage partitions
within a Browsing Context Group?  I'm not sure if that would be disruptive
in practice (maybe not?), or if it would be sufficient to block all ways
that B1 and B3 might find each other.

Charlie

On Wed, Aug 30, 2023 at 10:38 AM Ari Chivukula <[email protected]> wrote:

> *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
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGpy5DLTmXFYhFZScCSPcEsUrj9WiN-KAcosf_fOprQPcYy2og%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CAH%2B8MBZX2T6UE8%2B2kVPY8t5xwFDZhCxoTc0f4BNGOKk1QUAQTw%40mail.gmail.com.

Reply via email to