Hacker News Reader

Comment by AlexandrB | Hacker News Reader

> A Google spokesperson has been in touch to say the issue is a programming error, and will be fixed: "We are aware of a bug in Chrome that is impacting how cookies are cleared on some first-party Google websites. We are investigating the issue, and plan to roll out a fix in the coming days."

It's really hard to give Google the benefit of the doubt at this point.

View on HN

I'm sure it was working before because I re-call removing everything and was unlogged from Google.

Wouldn't this make it even worse? It worked correctly, then they changed it to _not_ work for their sites?

The source is public and the version history too, so you don't need to assume, you can look. If you don't see anything particular, you may assume that it's a bug and wasn't easily visible to the developers either.

This will most likely be a patch the product bits pf Chrome, not chromium. The bug isn't in Edge.

https://chromium.googlesource.com/chromium/src.git/+/f800edb...

Here's the fix, the bug is in chromium but only affects chrome because it has some "Hosted Apps" installed out of the box.

You are talking about Chrome or Chromium?

When I looked at the source, around 2015, there wasn't much difference, other than the name. People called "Google" were allowed to name the result of building it "Chrome". If you weren't Google you had to call it Chromium, and could of course apply patches or change the build flags. The functional differences I saw then were all a result of patches that were applied by my distribution.

Where you'd assume clearing Cookies to be as simple as cookieStore.clear() - I can imagine it's due to some legacy remainder of times when they did do everything to track without consent.

Reply on news.ycombinator.com