[saberworks]

My experience has been the opposite. It breaks every Amazon Pay integration and a lot of Paypal integrations as well. It also breaks online banking for the two credit unions I use, both of which seem to use some 3rd party service to run their backends. And then just whitelisting the domain isn't a great solution because then that means they can drop any 3rd party cookies, not just the desirable ones. So suddenly my online banking works, but now I've got google trackers and whatever other crap they want to drop. I believe I was able to whitelist just those cookies but that was quite a few versions ago and the interface is different now so I can't find where I did it. The cookie interface is really terribe; when you go to the site information it tells you whether the site is storing any cookies, and many times it says "No" but if you click the "view cookies" link it shows a ton of them. This happens when the domain doesn't match exactly (for example www.example.com vs example.com) so you can't really trust the Yes|No info box.

[forapurpose]

> whitelisting the domain isn't a great solution because then that means they can drop any 3rd party cookies, not just the desirable ones

Try something like uMatrix or similar add-ons. They allow you to configure rules similar to application firewalls:

  cookie * * DENY
  cookie * 1stparty ALLOW
  cookie creditunion.org finserv.com ALLOW

Great interface too, at least what I've seen on uMatrix: Most rules are configured with one click in a 'matrix' of hosts and applications.