From a6e5eb38df6ce7c00fd35594653e42f4f634de6b Mon Sep 17 00:00:00 2001 From: Andrew Williams Date: Wed, 2 Feb 2022 13:30:56 -0500 Subject: [PATCH 1/3] Replace origin with storage key for BroadcastChannel partitioning This PR updates the BroadcastChannel portion of the HTML standard to have storage keys be used instead of origins when determining which browsing contexts should be able to have BroadcastChannel messages sent and received from them. Today, a storage key only consists of an origin, but it will likely soon include the top-level origin as well. Only using origin enables certain forms of cross-site tracking. For more details, see: https://privacycg.github.io/storage-partitioning/ --- source | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/source b/source index a2fb0bdf235..16c1f62e015 100644 --- a/source +++ b/source @@ -4126,6 +4126,7 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute @@ -102375,6 +102376,11 @@ interface BroadcastChannel : EventTarget {
  • Let sourceOrigin be this's relevant settings object's origin.

  • +
  • Let sourceStorageKey be the result of running obtain a storage key + with this's relevant settings object.

  • + +
  • If sourceStorageKey is failure, then return.

  • +
  • Let destinations be a list of BroadcastChannel objects that match the following criteria:

    @@ -102382,9 +102388,8 @@ interface BroadcastChannel : EventTarget {