Why we Forked Firefox and Not Chromium

Re:Why we Forked Firefox and Not Chromium by emn13 on Wednesday December 18, 2019 @03:16PM (#21828940)

I'm seriously skeptical of that. It's plausible they didn't bother trying to get it to work in FF, and just thought "screw that". But judging by de screenshot of the stock price history alone, clearly FF has no trouble rendering that history - both screenshots are FF, right? It's only the UA header that was changed.

Incidentally, this is far from the first time google has been caught heavily optimizing exclusively for their own browsers, which, to be clear, is quite probably not explicit policy - but is monopolistic abuse nonetheless. Remember the youtube polymer redesign? The Edge HW acceleration-breaking invisible layers? I get the feeling they just don't test in other browsers nearly as well.

[ Parent | on HN ]

Re:Why we Forked Firefox and Not Chromium by bagacrap on Wednesday December 18, 2019 @04:04PM (#21829438)

A static screenshot does not fully capture the functionality of a web element, hence my use of the term "subtly".

[ Parent | on HN ]

Re:Why we Forked Firefox and Not Chromium by emn13 on Thursday December 19, 2019 @03:13PM (#21838764)

Occam's Razor suggests you're looking for ghosts, and just to be sure I tried this on my phone: as far as I can tell behaviour using FF + chrome UA addon (which I specifically installed to test this) is indistinguishable from chrome as far as google search's stock ticker display goes. focusing points, time spans, toggle modes, clicking the extra-info chevron... all no difference.

Given google's history here you really shouldn't be giving them the benefit of the doubt in this matter; at best they're consistently, repeatedly negligent; but it's at least conceivable there's culture of giving additional other google teams; which is a form of monopolistic power abuse.

[ Parent | on HN ]