With 3p Cookies blocked in Chrome, JS SetCookie events seem to be detected but don't cause blocking

[pde]

(As discussed on Mattermost). I think I the issue I was observing with lots of unblocked trackers on pages like Chicago Tribune articles was several different issues at once. In addition to circumvention of content blocking by that page, it seems that when third party cookies are blocked in Chrome, PB notices the set cookie events but doesn't actually red/yellow list because of them?

[ghostwords]

@pde Privacy Badger is indeed affected when third-party cookies are disabled, as Chrome seems to block writing of cookies and localStorage by third parties. Privacy Badger still gets to learn from Set-Cookie headers sent by third parties, however.

I am not sure there is anything to do here other than to update the FAQ entry for what happens when you disable third-party cookies.

[ghostwords]

We should investigate what the Privacy Badger experience is like with third-party cookies disabled, see whether we can do anything to improve it (such as perhaps detect failed JavaScript cookie events), and document the differences using Badger with and without third-party cookies.

[ghostwords]

FAQ entry updated: https://github.com/EFForg/privacybadger/wiki/Home/_compare/0c3cb962825dd2577304a71dae6d8da7ae87a3fe...a4503008e228da461614ecc2bd09e381c3c4c46a

[ghostwords]

This answer now lives on the homepage FAQ: https://www.eff.org/privacybadger/faq#Does-Privacy-Badger-still-work-when-blocking-third-party-cookies-in-the-browser