Does google try to sabotage IE?

xandros9

Active member
Nov 12, 2012
16,107
0
36
Visit site
If you want to check it out, use the F12 Dev Tools to change the UA of IE to something like Chrome to see if anything's different.
 

IlkkaV

New member
Nov 8, 2013
22
0
0
Visit site
^ Interesting. What UA strings, specifically for mobile browsers, did you test with besides chrome, safari and IE?

I installed User Agent Switcher add-on to desktop Chrome and checked iOS, Android, and WP7 UA's there. I also added a WP8 UA "Mozilla/5.0 (compatible; MSIE 10.0; Windows Phone 8.0; Trident/6.0; IEMobile/10.0; ARM; Touch; NOKIA; Lumia 920)" there, and the end result was the same as in WP7.
 

bsayegh

New member
Feb 10, 2013
301
0
0
Visit site
To some degree I believe that they target webkit browsers and just let IE either succeed or fail on their own. Last night, however, I had an issue on youtube that I have never seen and it kind of leads me back to my original "anti-IE" conspiracy theory. I was watching a video and I clicked on the Youtube home link, and it didn't do anything. I clicked it several times. I started the debugger but pretty much got lost in a sea of minified code (even after formatting the code it was hard to figure out what was going on).

The home link shouldn't do anything other than take you back home, should it? Maybe they record some metrics before you leave or something, but that link should work. I refuse to believe they are using some link that is so fancy that it works in a webkit browser and it doesn't work in IE.
 

Reflexx

New member
Dec 30, 2010
4,484
4
0
Visit site
Remember when people were up in arms about MS making their own branch of Java? Java was just so limited. But because of the backlash, MS left Java and created C#.

But here is Google trying to pretty much take over the web and people fall right in line.
 

a5cent

New member
Nov 3, 2011
6,622
0
0
Visit site
I installed User Agent Switcher add-on to desktop Chrome and checked iOS, Android, and WP7 UA's there. I also added a WP8 UA "Mozilla/5.0 (compatible; MSIE 10.0; Windows Phone 8.0; Trident/6.0; IEMobile/10.0; ARM; Touch; NOKIA; Lumia 920)" there, and the end result was the same as in WP7.

Well you see, this is my point. That doesn't necessarily mean Google is singling out IE. You would have also had to test a few other non-webkit based mobile browsers, like Opera. Only if they also all worked correctly, could we start suspecting IE is being singled out for 'special treatment'.

Based on those tests, I'd suspect Google does the same thing they do on their other sites...

"this is what works with webkit, see what works for you"

I'm not saying you are wrong. You could be right. We just need be careful before going too far with accusations.

I refuse to believe they are using some link that is so fancy that it works in a webkit browser and it doesn't work in IE.


That I wouldn't believe either. Strange...
 
Last edited:

IlkkaV

New member
Nov 8, 2013
22
0
0
Visit site
Well you see, this is my point. That doesn't necessarily mean Google is singling out IE. You would have also had to test a few other non-webkit based mobile browsers, like Opera. Only if they also all worked correctly, could we start suspecting IE is being singled out for 'special treatment'.

Based on those tests, I'd suspect Google does the same thing they do on their other sites...

"this is what works with webkit, see what works for you"

I'm not saying you are wrong. You could be right. We just need be careful before going too far with accusations.

You're right. I managed for a while forget that both Android and iOS do use a webkit-based browser and they seem to be delivering the Communities option only to webkit-based browsers as e.g. Firefox OS UA string also gave the version without the Communities option. Seems like I was a little too quick to jump to conclusions based on Google's earlier behavior. However, I'm still wondering whatever happened to the "don't check for user agent, test for features instead" recommendation here.
 

bsayegh

New member
Feb 10, 2013
301
0
0
Visit site
I do believe it could just be a matter of testing for webkit and ignoring other browsers (IE), but I am also amazed at how complex their javascript must be in order for IE 11 not to support it. Why would the back button do something different in IE than it does in Chrome or even Fire Fox? Why would it take me down to the comments section instead of to the previous page in my history? Im guessing there is an anchor that links to the comments section, but I cant imagine why they would hijack my history to take me to the comments section. I THINK the screen scrolls down a little at the end of a video to show the Sharing options, but that should work without messing with my history.

IE 11 has pretty strong support of the Html 5 and CSS 3 standards. It isn't 100%, but it should be close enough to support what Google is trying to do. I could maybe see gchat having problems since its a little more complex than a home link or a back button, but my problem with gchat is that I get logged out of it. I don't think that is happening on the client.

Maybe ill download a browser that isn't IE or FireFox (FF seems to be pretty well supported by Google's sites) and see how things work.
 

a5cent

New member
Nov 3, 2011
6,622
0
0
Visit site
but I am also amazed at how complex their javascript must be in order for IE 11 not to support it.
<snipped>
Maybe ill download a browser that isn't IE or FireFox (FF seems to be pretty well supported by Google's sites) and see how things work.

Okay, I'll say it. This has absolutely nothing to do with the complexity of the code behind that button. In the second line I quoted, you yourself provided the real reason why this happens... you'll download another browser... maybe Chrome, or at least something based on Webkit.

Google has (or at least had - I haven't checked for a while) a few services which serve a sub-par version of their website to IE (or any other non webkit based browser), despite IE being fully capable of handling the code of their deluxe version, which they reserve for people using a browser that they control, either partially (any Webkit browser), or fully (Chrome). Although in some cases the code really is very proprietary (like Google Maps), in most cases it's just because Google wants consumers to think that all browsers except the ones they control are crippled. Then more people switch. Google cripples more. More people switch... and so on...

It's quite effective.

Finally, Google doesn't do a good job supporting FireFox. FireFox does a good job of supporting Google. The Mozilla group felt they had to mimic some of Google's proprietary features to keep their browser viable. Microsoft once chose to do the same, but their Enterprise customers demanded a standards compliant HTML renderer, so they had to backtrack.
 
Last edited:

bsayegh

New member
Feb 10, 2013
301
0
0
Visit site
Okay, I'll say it. This has absolutely nothing to do with the complexity of the code behind that button. In the second line I quoted, you yourself provided the real reason why this happens... you'll download another browser... maybe Chrome, or at least something based on Webkit.

Google has (or at least had - I haven't checked for a while) a few services which serve a sub-par version of their website to IE (or any other non webkit based browser), despite IE being fully capable of handling the code of their deluxe version, which they reserve for people using a browser that they control, either partially (any Webkit browser), or fully (Chrome). Although in some cases the code really is very proprietary (like Google Maps), in most cases it's just because Google wants consumers to think that all browsers except the ones they control are crippled. Then more people switch. Google cripples more. More people switch... and so on...

It's quite effective.

Finally, Google doesn't do a good job supporting FireFox. FireFox does a good job of supporting Google. The Mozilla group felt they had to mimic some of Google's proprietary features to keep their browser viable. Microsoft once chose to do the same, but their Enterprise customers demanded a standards compliant HTML renderer, so they had to backtrack.

Okay, thanks for clarifying.

If Google is using these shady (albeit effective) practices, then why doesn't MS do the same thing? Sure many of the popular sites are owned by Google, but the most popular OS is owned by MS. They COULD make running Chrome on a Windows machine a nightmare. I am not saying that they should (it isn't very ethical and might make them look bad in the end), but Google started it. They have given themselves an unfair advantage that was essentially stripped of MS years ago (simply because Windows came preloaded with IE).

I wouldn't say Google gets away with everything. They seem to be on trial for unfair business practices all the time. I think this is just specifically frustrating to me because I prefer IE in general, especially since it has become must faster and cleaner.
 
Last edited:

a5cent

New member
Nov 3, 2011
6,622
0
0
Visit site
If Google is using these shady (albeit effective) practices, then why doesn't MS do the same thing? Sure many of the popular sites are owned by Google, but the most popular OS is owned by MS. They COULD make running Chrome on a Windows machine a nightmare. I am not saying that they should (it isn't very ethical and might make them look bad in the end), but Google started it. They have given themselves an unfair advantage that was essentially stripped of MS years ago (simply because Windows came preloaded with IE).

Well, on the mobile web that is impossible at this point. Webkit owns 95% of mobile web traffic, so if MS used the same tactic, they would be crippling their websites for 95% of consumers. That is the exact opposite of how it works for Android and iOS, which is an absolute necessity for the tactic to be affective. Not to mention that no version of mobile IE currently exists that runs on Android or iOS, so even if consumers wanted to, they wouldn't be able to switch to IE to improve their browsing experience on MS' websites.

For the desktop I do not know. I can only guess. Note however, that Google is also much more well behaved on the desktop than they are on mobile. Google could easily claim that the differences are down to bugs or just small oversights.
 

Staff online

Members online

Forum statistics

Threads
323,294
Messages
2,243,585
Members
428,054
Latest member
moocher720