Hacker News Reader

Comment by ars | Hacker News Reader

Chrome is open source, right? So can we see the bug and judge if it really does seem like an innocent bug?

> 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/+/f800edb...

[2] https://chromium-review.googlesource.com/c/chromium/src/+/21...

Thanks 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).

Chrome is not open source, it's a derived proprietary superset of the open source Chromium. They are not the same thing in very material ways

Only a few things are different in Chrome. Notably, it has the ability to send crash reports and metrics, play proprietary audio codecs, some Google API keys are added (eg. safe browsing, speech, web store), and the Widevine component to enable DRM. Nothing is different in the core code of the browser.

https://chromium.googlesource.com/chromium/src/+/master/docs...

> in very material ways

No pun intended?

Each user's version of Chrome is not necessarily the same. As a result of field trials/variations, some Chrome users are running code that is not yet (and may never be) available to the public.

https://textslashplain.com/2017/10/18/chrome-field-trials/

https://www.ghacks.net/2013/04/05/field-trials-in-chrome-how...

https://stackoverflow.com/questions/12183575/what-is-followi...

Reply on news.ycombinator.com