Contact emails
wande...@chromium.org, m...@chromium.org, mike...@chromium.org
https://github.com/wanderview/quota-storage-partitioning/blob/main/explainer.md
We’re actively working on adding the relevant spec concepts with the following WIP PRs (there has been some extensive refactoring requested, so it’s taken longer than anticipated):
https://github.com/whatwg/html/pull/8447
https://github.com/whatwg/html/pull/8036
https://github.com/whatwg/html/pull/8027
https://github.com/whatwg/storage/pull/144
We intend to partition a number of APIs in third-party contexts. This effort is focused on partitioning APIs above the network stack. This includes quota-managed storage, service workers, and communication APIs (such as BroadcastChannel). See the explainer for more details:
https://github.com/wanderview/quota-storage-partitioning/blob/main/explainer.md
Early Design Review https://github.com/w3ctag/design-reviews/issues/629
Closed as “Satisfied”
Gecko: Shipped/Shipping
WebKit: Shipped/Shipping
Web developers: Mixed signals
Other signals:
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
We’re still investigating the risk for WebView, and if we should ship in that context at a later date.
We propose to ship two separate deprecation trials, each for approximately one year (to give sites plenty of time to test and update, if needed). Aspirationally, we would like to ship partitioned storage in M112, and our goal is to have a deprecation trial available from M111 to M123.
The first is a general-purpose deprecation trial that will allow a top-level site to opt into unpartitioned storage, service workers, and communication APIs for third-party contexts embedded in its site. This will give sites more time for testing and migrating to solutions that don’t require partitioned storage.
The second is tailored to a behavior we discovered during the dev-trial that is known to be used by the Firebase Auth library. This deprecation trial only allows for unpartitioned `sessionStorage` across a navigation (which is how the `signInWithRedirect()` method relies on storing and postMessage’ing authentication tokens). The Firebase team is aware of the issue (as it also affects Safari users; Firefox has worked around the breakage by granting unpartitioned storage via a shim), and is working to migrate their users to cross-browser solutions that are compatible with partitioned storage. Given the different nature of the Firebase issue, we think it makes sense to ship a different deprecation trial entirely.
DevTools has support for partitioned storage.
Yes for all others; TBD for WebView.
Yes
https://developer.chrome.com/en/blog/storage-partitioning-dev-trial
ThirdPartyStoragePartitioning
DisableThirdPartySessionStoragePartitioningAfterGeneralPartitioning
False
https://bugs.chromium.org/p/chromium/issues/detail?id=1191114
https://bugs.chromium.org/p/chromium/issues/detail?id=1191709
https://chromestatus.com/feature/5723617717387264
--
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 blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/d395956d-3a59-1ba9-1b5c-33505e1518d3%40chromium.org.
Thanks!
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfU0yW_XD5EVtdb-D%3Deh%2BUE3oobKGE4yub9duP7aJtNK5g%40mail.gmail.com.
Hello - would you mind filing an issue at
https://github.com/miketaylr/partitioned-storage-deprecation-trial-feedback
for discussion?
Hi there,
Find attached an explanation on what is not working for us.
Kind regards,