3 ms·
> Chrome is open source, right? So can we see the bug and judge if it really does seem like an innocent bug? Not sure what the sibling comments are talking abo
by magicalist 6y ago
> Chrome is open source, right? So can we see the bug and judge if it really does seem like an innocent bug?
Not sure what the sibling comments are talking about. The bug fix[1] links the original change that introduced the bug[2].
[1] https://chromium.googlesource.com/chromium/src.git/+/f800edbd1b50ecc13a0d3391f5f45ba9c84625be%5E%21/ https://chromium.googlesource.com/chromium/src.git/+/f800edb...
[2] https://chromium-review.googlesource.com/c/chromium/src/+/2181827 https://chromium-review.googlesource.com/c/chromium/src/+/21...
- CGamesPlay 6y agoThanks for digging this up! It only addresses the YouTube half, but if memory serves the Google half is due to a mandatory deep integration between browser profiles and Google cookies. I'm unclear if they classified that one as a "bug" (not that it really matters since they use custom HTTP headers to implement tracking for google properties).