Subscribe to Chrome for Developers → goo.gle/ChromeDevs
10 หลายเดือนก่อน +3
Why some of the links in column name in a website doesn't have the cookies tab, next to time tab? The majority of the website I am browsing don't have that.
So 3rd party cookies still technically DO exist right? Its just that 3rd party cookies with SameSite=None will also need a partition key? Is that right?
For a cookie to work cross site it HAS to set the attribute SameSite=None (that also requires the Secure attribute to be set). Otherwise, Chrome already blocks the cookie in cross-site contexts. The description has a link that explains in detail the SameSite attribute. Some of the functionality that was traditionally implemented using third-party cookies can be accomplished by using the partitioned attribute, but other use cases will need to migrate to other APIs like Storage Access API. All the details about to figure out what is the best migration out are in the other link in the description, the guide to prepare for the end of third-party cookies.
@@ajaras Thanks for the response. I did some testing with s where the domain is different from the top level domain. I completely understand the concepts of Samesite=None; Secure; Partitioned; cookies now. When you load that same Iframe on ANOTHER domain, the partition key for the cookie within the does not match... and the cookie is gone. Without Partition; that cookie would be visible but with a warning... for now.
where is the "Name" panel? Mine looks nothing like what you're showing in dev tools at 1:53 mark in the video. Any assistance would be appreciated. Actually I don't have a cookies tab in that view either. Is there a different setting?
Subscribe to Chrome for Developers → goo.gle/ChromeDevs
Why some of the links in column name in a website doesn't have the cookies tab, next to time tab? The majority of the website I am browsing don't have that.
So google tracking cookies are gonna be hit too, right?
So 3rd party cookies still technically DO exist right? Its just that 3rd party cookies with SameSite=None will also need a partition key? Is that right?
For a cookie to work cross site it HAS to set the attribute SameSite=None (that also requires the Secure attribute to be set). Otherwise, Chrome already blocks the cookie in cross-site contexts. The description has a link that explains in detail the SameSite attribute. Some of the functionality that was traditionally implemented using third-party cookies can be accomplished by using the partitioned attribute, but other use cases will need to migrate to other APIs like Storage Access API. All the details about to figure out what is the best migration out are in the other link in the description, the guide to prepare for the end of third-party cookies.
@@ajaras Thanks for the response. I did some testing with s where the domain is different from the top level domain. I completely understand the concepts of Samesite=None; Secure; Partitioned; cookies now. When you load that same Iframe on ANOTHER domain, the partition key for the cookie within the does not match... and the cookie is gone. Without Partition; that cookie would be visible but with a warning... for now.
where is the "Name" panel? Mine looks nothing like what you're showing in dev tools at 1:53 mark in the video. Any assistance would be appreciated. Actually I don't have a cookies tab in that view either. Is there a different setting?
👍 thank you
Thank you for watching!
Veri nice TH-cam ji