[MSFT_Edging]

A few weeks ago I posted on here about the maps lag, and it literally felt like it was fixed after the comment got some attention.

There's 100% targeted de-optimization for firefox users and the burden of finding it is on the users it seems.

[Pathogen-David]

Not to diminish the other sketchy stuff Google's doing, but I think the maps lag issue might actually be Firefox's fault. Whenever it happens to me WebGL stops working across all websites and restarting the entire browser fixes it. It's almost like when Firefox has been open a long time it just forgets how to use graphics acceleration.

[MSFT_Edging]

The thing that bothered me is it didn't always happen, at one point there was performance parity, and things changed in a way that specifically worked worse in firefox.

Which means:

A) Firefox had bad webgl implementations(I didn't experience what you did, but I wont say it doesn't happen) and google added features that regressed the experience on other browsers.

B) Google knowingly made performance worse on Firefox, regardless of webgl implementations.

C) Google leverages its own browser to only test on their browser, to influence the market to have to use googles browser in order to use their services(not the same as the IE/Windows monopoly lawsuit, but sure smells like it).

[gbraad]

i believe for anything non-Chrome? Even Vivaldi has issues with some Google products.