I think that Mozilla's recent re-launch of Lightbeam (nee Collusion) shows that they're not trying to back away from the issue of third-party cookies. The complication is that you need to find a solution that doesn't break enough sites that users give up and switch to less-privacy-conscious browsers, which would completely defeat the purpose.
Comments
I think that Mozilla's recent re-launch of Lightbeam (nee Collusion) shows that they're not trying to back away from the issue of third-party cookies. The complication is that you need to find a solution that doesn't break enough sites that users give up and switch to less-privacy-conscious browsers, which would completely defeat the purpose.
How does it break sites? I use Safari, where this setting is the default, and everything seems Ok.
safari use case means nothing. it is disabled only if the 1st class site does not set a cookie or something futile like this.
you probably have 3rd party cookie working as usual.