4 ms·
I'm glad Firefox is doing this, but ... > Blocking third-party cookies can break some site that rely on third-party resources Can anyone name sites that requi
by hackuser 10y ago
I'm glad Firefox is doing this, but ...
> Blocking third-party cookies can break some site that rely on third-party resources
Can anyone name sites that require them?
As someone who defaults to deny all cookies and manually enables every one my browser accepts, I don't think I've found a site that requires 3rd-party cookies. Few sites require cookies unless you login or have shopping cart.
Of course, that's anecdotal. Maybe I just don't visit certain categories of sites and don't encounter them.
- baraah 10y agoI think I remember allowing them to watch Thursday Night Football on Twitter. I can't find anything about third-party cookies and tnf.twitter.com on Google though.
- driverdan 10y agoI've been blocking 3rd party cookies for years. I think I've seen less than five sites break.
- biggerfisch 10y agoMy university uses Piazza often as a forum, linked in through our course management site, Canvas. If you don't have 3rd party cookies, it used to just not work, but not it redirects you into opening a new tab/window for Piazza. It's still annoying and would be nice to have it right there in Canvas
- ukyrgf 10y agohbogo.com relies on third party cookies from my cable company.
- g4k 10y agoThe Shopify plugins from Bold use them.
- sleavey 10y agoStackOverflow, sadly. Their Javascript requires some off site cookies to allow for their cross domain user account stuff. Not enabling third party cookies on the StackExchange sites leads to broken pages.
- untoreh 10y agoWouldn't that be the case for any site using sso?
- sleavey 10y agoYes, though there are some ways around this. You could send the user to another domain to sign in using a unique request ID that identifies the user. After authenticating this unique ID can be communicated back to the first site to show the user has authenticated, and a cookie could keep the session information. That wouldn't give a seemless sign-in on every site, though - you'd need one cookie (and one sign-in) per domain. The other way is to have all StackExchange sites be subdomains of stackexchange.com - which is how the designers of the web intended it to be, I think.
- kuschku 10y agoGoogle. The entire notification center, cross-site hangouts chat, etc all requires third-party cookies.
- toyg 10y agoQuidco.com and similar referral-promotion sites.