4 ms·
> The popular Total Cookie Protection moves from the optional strict setting to always-on in private browsing. This feature maintains a separate “cookie jar” fo
by nfoz 5y ago
> The popular Total Cookie Protection moves from the optional strict setting to always-on in private browsing. This feature maintains a separate “cookie jar” for each website you visit while browsing privately. Any time a site deposits a cookie, Firefox locks it up in its own cookie jar so that it can’t be shared with any other website.
Why isn't that on all the time, even in normal browsing mode? Like, what breaks because of that? I thought cookies were locked per-domain since the invention of cookies.
- spartanatreyu 5y ago> Why isn't that on all the time, even in normal browsing mode? Like, what breaks because of that? Traditionally speaking, anything with a "Login with facebook/google/microsoft/apple account" would break, because the cookie wouldn't be able to work across domains. This isn't the case now though, mostly...
- zmmmmm 5y ago> I thought cookies were locked per-domain since the invention of cookies That is sort of what this mode breaks. Even if your web page on foo.com loads an image from bar.com, bar.com still cant set a cookie that it will get back next time you go to bar.com. So cookie's aren't "per-domain" any more, they are something much more complicated. And yes, it breaks stuff .... so if for example, if you watch an embedded Youtube video on page A, youtube probably doesn't know its you and if you signed into Youtube previously as a suscriber to avoid ads guess what, you're now going to look anonymous and you'll get treated to ads even if you pay to not have them on Youtube normally.