The cause of this on Chromium 112 is evidently rooted in at chrome://flags
Experimental third-party storage partitioning.
Enables partitioning of third-party storage by top-level site. Note: this is under active development and may result in unexpected behavior. Please file bugs at https://bugs.chromium.org/p/chromium/issues/entry?labels=StoragePartitioning-trial-bugs&components=Blink%3EStorage. – Mac, Windows, Linux, ChromeOS, Android, Fuchsia, Lacros
See privacycg/storage-partitioning#25 https://groups.google.com/a/chromium.org/g/net-reviews/c/itOHk-vM8r8.
Either disable at chrome://flags or launch with --disable-features=ThirdPartyStoragePartitioning flag for a chrome-extension: protocol iframe appended to a document on the Web to be set as WindowClient and ability to get the active MV3 extension ServiceWorker with navigator.serviceWorker.getRegistrations().
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/b4164ccc-1596-473c-b5a5-0355a3049c5bn%40chromium.org.