sessionStorage read fails when storage partition is enabled #89
-
|
Hello I am using Chrome 109 with flag 'Experimental third-party storage partitioning' enabled and 'Block all third party cookies selected' |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 17 replies
-
|
Hi @vinothvk - this is currently expected behavior. When a user enables "Block all third party cookies", it also disables all storage in a 3rd party context. Once partitioned 3P storage is launched, it may be the case that we later enable [partitioned 3P storage] for the "Block 3P Cookies" settings, but have no plans to announce today. (edited for clarity, hopefully) |
Beta Was this translation helpful? Give feedback.
-
|
@vinothvk perhaps I don't follow - once storage partitioning ships, embedded applications will still have storage, it will just be partitioned with the top-level site. Or do you need access to unpartitioned storage set from the 1P context? |
Beta Was this translation helpful? Give feedback.
-
|
@miketaylr The use case is, 3rd party embedded applications to have access to their own partitioned storage, when privacy sandbox rolls out live / chrome's block 3rd party cookies settings enabled. |
Beta Was this translation helpful? Give feedback.
-
|
@miketaylr any updates on this |
Beta Was this translation helpful? Give feedback.
-
|
Apologies for the delay.
This will be true, once we ship partitioned storage
Initially, when 3rd party cookie blocking is turned on, storage will be disabled (this is the current state today - no change from the status quo). We haven't yet scoped out the work to turn on partitioned storage when 3rd party cookie blocking setting is enabled, but it's on our list of priorities for this year. Does that answer your question @vinothvk? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for confirming @miketaylr . Appreciate it. I have a basic question not related to this thread, I believe privacy sandbox and block 3p cookies in chrome are two different things. Is that correct ? If so, what are the differences? |
Beta Was this translation helpful? Give feedback.
-
|
Good question. "Privacy Sandbox" is an effort to prevent cross-site tracking and improve privacy generally. See https://privacysandbox.com/open-web/#how-works-on-web-hero. Removing 3P cookies is part of that plan, but it encompasses many other things (new APIs related to Ads or Ads use cases, reducing passive entropy collection, etc). |
Beta Was this translation helpful? Give feedback.
-
|
@miketaylr in march 2023 you have mentioned below, by any chance is it planned to be released this year ? Initially, when 3rd party cookie blocking is turned on, storage will be disabled (this is the current state today - no change from the status quo). We haven't yet scoped out the work to turn on partitioned storage when 3rd party cookie blocking setting is enabled, but it's on our list of priorities for this year. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @vinothvk - yep, this has landed just this week. You should be able to test in the latest Canary version (119.0.6039.0 or higher). https://chromiumdash.appspot.com/commit/6bf7d85273b2192b3255e5e7cd345a3b69dd4d4b |
Beta Was this translation helpful? Give feedback.
Apologies for the delay.
This will be true, once we ship partitioned storage
Initially, when 3rd party cookie blocking is turned on, storage will be disabled (this is the current state today - no change from the status quo). We haven't yet scoped out the work to turn on partitioned storage when 3rd party cookie blocking setting is enabled, but it's on our list of priorities for this year.
Does that answer your question @vinothvk?