Is Google Burying Firefox With User Agent Strings?

That question is answered in the second part. Changing Chrome's UA string to anything other than default causes errors, so the browsing speed can't be tested.

Re: Is Google Burying Firefox With User Agent Strings?

#6

Post by tomerv » Sun, May 06, 2012, 12:14 PM UTC

Does this mean that Google has given up completely on net neutrality? This is a very bad notion.

Re: Is Google Burying Firefox With User Agent Strings?

#7

Post by StavrosK » Sun, May 06, 2012, 12:16 PM UTC

ddorian43 wrote: post #4

StavrosK wrote: post #3

What if you change Chrome's UA string to Firefox's?

he did on the second page and problems started happening

Whoops, sorry, I must have missed that part.

Re: Is Google Burying Firefox With User Agent Strings?

#8

Post by mgkimsal » Sun, May 06, 2012, 12:17 PM UTC

I've been pretty consistent in my Firefox use the past few years (probably >80% of my browsing is in Firefox), and I've never encountered this. Ever. I'm doing nearly all of this from OSX, with occasional browsing from FF and IE in a Windows VM or FF in a Linux VM.

Perhaps this is more to do with a Linux string being picked up vs the Firefox aspect?

Re: Is Google Burying Firefox With User Agent Strings?

#9

Post by udp » Sun, May 06, 2012, 12:18 PM UTC

mgkimsal wrote: post #8

I've been pretty consistent in my Firefox use the past few years (probably >80% of my browsing is in Firefox), and I've never encountered this. Ever. I'm doing nearly all of this from OSX, with occasional browsing from FF and IE in a Windows VM or FF in a Linux VM. Perhaps this is more to do with a Linux string being picked up vs the Firefox aspect?

I've also used nothing but Firefox for the past few years, and I'm a Linux user. I've never experienced anything like the author describes.

Re: Is Google Burying Firefox With User Agent Strings?

#10

Post by jezclaremurugan » Sun, May 06, 2012, 12:19 PM UTC

I've had the same problem while loading Gmail in Debian, but I blamed it on the nightly build without checking.

However, Firefox nightly builds on Windows work without a hitch. I am suspecting some firefox+linux combination messing things up. My two cents.

Try in windows, might give more leads...