Bryan Wong

Please see attached screen recording. I have enabled [#test-third-party-cookie-phaseout](chrome://flags/#test-third-party-cookie-phaseout) in chrome://flags and also disabled all third party cookies in chrome://settings/trackingProtection. https://github.com/GoogleChromeLabs/privacy-sandbox-dev-support/assets/26299742/c7e4d32d-812b-416a-909c-992183a250d9

I restarted chrome multiple times. Unable to send screenshot of chrome://flags atm, but I have enabled the third party cookies deprecation flag and that’s it On Mon, Feb 12, 2024...

here is a SS of my chrome://flags page

@wanderview I have not added a cookie exception for Figma. See attached screenshot (the omnibox says third party cookies are blocked, but the issues panel disagrees): @samdutton I have hard...

@wanderview There is no entry for "CookiesAllowedForUrls" and figma.com is not listed in any of the policy domains. I just found this page: https://github.com/amaliev/3pcd-exemption-heuristics/blob/main/explainer.md and though this is related, but...

I’m not sure if that is true. If third party cookies are truly being blocked on that page then the app I am loading should NOT be able to authenticate...

@wanderview This is strange. I asked a coworker to block 3PC and opt into the 3PCD flag and test it. He is experiencing the same issue as I am where...

chrome://flags chrome://settings/trackingProtection

Disabling #test-third-party-cookies-phaseout and enabling #tracking-protection-3pcd works for me. thank you for the help! I think I should flag here that enabling #test-third-party-cookies-phaseout not only causes the message shown above, but...