Implement cookie blocking for whitelisted sites about privacybadger HOT 3 CLOSED

This has been partially done via e363fae, but needs more work:

1. Clobbering cookie-getting code needs to be tested
2. What do we do about Disqus?

from privacybadger.

I now think a cleaner way to do this is to use chrome.privacy.website to just turn on third-party cookie blocking and change lots of other privacy settings too. There are issues, though. I don't see a way to get notified of a cookie-setting event that was blocked by Chromium's third-party cookie blocking user preference, even though this must be tracked since users can see a cookie icon in the URL bar when this happens. Without this information, we cannot use chrome.cookies API to add things to a whitelist. We could just change the cookie setting and leave the user in charge, but this isn't ideal. Still, I think this approach is better than trying to do the document.cookie clobbering ourselves.

from privacybadger.

Per our discussion, the target is to do clobbering only for third party frames, another issue is open about this.

from privacybadger.