Live data from Hacker News

IE11 on Windows 8.1 - Google Search loads in legacy mode

productforums.google.com

21–30 of 67 posts

Re: IE11 on Windows 8.1 - Google Search loads in legacy mode

#21
post #19

Earlier quoted context omitted.

"For a site like Google, I see no reason why Microsoft should have put it into compatibility mode- I have to assume that Google does testing on IE and any bugs should have been addressed quickly by Google." Unfortunately, we see otherwise during our compat testing here at Microsoft on many occasions.

I guess you have no way to work with a major company like Google since you are such a small organization lacking resources.

You're making an assumption that Microsoft are the blocker. Let's just say that it's a two-way street when it comes to communication.

Re: IE11 on Windows 8.1 - Google Search loads in legacy mode

#22
post #20

Earlier quoted context omitted.

Unless it was google.. "Hey, if we make Google uglier, maybe people will use Chrome!" "Probably, they are used to IE not working" Not sure who had the slip-up, but evil works both ways :P

> IE11 -> Tools -> Compatibility View Settings. > Remove check on "Use Microsoft Compatibility lists". That's the solution posted in that thread. It's an IE problem.

Tweaking Firefox to send the same user-agent string "Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.3; WOW64; Trident/7.0)" causes the exact same problem. It's a Google problem.

ETA: In standards mode, IE sends "Mozilla/5.0 (Windows NT 6.3; WOW64; Trident/7.0; rv:11.0) like Gecko".

Re: IE11 on Windows 8.1 - Google Search loads in legacy mode

#23
post #2

This seems to solve it: IE11 -> Tools -> Compatibility View Settings. Remove check on "Use Microsoft Compatibility lists".

I'm trying to figure out what the problem is, and I can't see how the compatibility list would force Google into such a legacy mode:

  google.com
It seems to read as: render and present as IE10, and if there is a `There's another section that overrides the backwards/forwards cache setting for google.com:

    
        ...
        google.com
But I've no clue how that would affect rendering so much.

I've disabled both settings (commented out) and will report back if commenting them out fixes Google.

Re: IE11 on Windows 8.1 - Google Search loads in legacy mode

#25
post #2

This seems to solve it: IE11 -> Tools -> Compatibility View Settings. Remove check on "Use Microsoft Compatibility lists".

I'm trying to figure out what the problem is, and I can't see how the compatibility list would force Google into such a legacy mode: google.com It seems to read as: render and present as IE10, and if there is a ` There's another section that overrides the backwards/forwards cache setting for google.com: ... google.com But I've no clue how that would affect rendering so much. I've disabled both settings (commented out…

If I were to guess:

Google is detecting the user agent string and attempting to use features that should be supported. e.g. google's code is trying to use some IE11 feature that IE10 didn't support. The compat settings are making this fail which seems to cause google's code to drop to it's lowest compatibility mode (IE 6?) as some sort of 'compatibility panic'.

Re: IE11 on Windows 8.1 - Google Search loads in legacy mode

#26
IE11 normally sends "Trident/7.0" and not "MSIE". Apparently Microsoft has added "google.com" to the Compatibility View List [1], which means IE11 now sends Google a User Agent that does include "MSIE". Google is interpreting this to mean it's an old version of IE, and sending the legacy view. You can manually disable the CVL, but then other sites that Microsoft has determined need old versions of IE won't work. I suspect Google will update their UA regexp soon, and this will be fixed, but it does sound like a Microsoft bug.

[1] http://msdn.microsoft.com/en-us/library/gg699485(v=vs.85).as...

(I work for Google, on unrelated things.)

Re: IE11 on Windows 8.1 - Google Search loads in legacy mode

#27
post #2

This seems to solve it: IE11 -> Tools -> Compatibility View Settings. Remove check on "Use Microsoft Compatibility lists".

I'm trying to figure out what the problem is, and I can't see how the compatibility list would force Google into such a legacy mode: google.com It seems to read as: render and present as IE10, and if there is a ` There's another section that overrides the backwards/forwards cache setting for google.com: ... google.com But I've no clue how that would affect rendering so much. I've disabled both settings (commented out…

I think the problem is that EmulateIE10 is slightly broken: it sends "MSIE 10" but also "Trident/7.0". Real IE10 has Trident 6.0. This looks like it's screwing up the UA regexes.

Re: IE11 on Windows 8.1 - Google Search loads in legacy mode

#28
post #19

Earlier quoted context omitted.

I guess you have no way to work with a major company like Google since you are such a small organization lacking resources.

You're making an assumption that Microsoft are the blocker. Let's just say that it's a two-way street when it comes to communication.

Sorry, I try to err on the side of caution as well but there is no way to do that in this case. Microsoft is clearly at fault. Adding someone to a "compatibility list" is a unilateral action Microsoft took.

If it works fine without being on compatibility mode, don't add it to your compatibility mode list.

Re: IE11 on Windows 8.1 - Google Search loads in legacy mode

#29
post #24
post #17

So nobody @ MSFT has access to Google.com before shipping off the product. Given that a typical engineer is so addicted to 'googling' all through the day, this would've been noticed.

Who says they use IE for googling? :-)

I've tried switching to Bing (kinda forced on a Lumia) and also sometimes when I can't find what I'm looking for with google. Without fail I've found myself switching back from Bing almost instantly even if I'm stuck with IE.

Re: IE11 on Windows 8.1 - Google Search loads in legacy mode

#30
post #28

Earlier quoted context omitted.

You're making an assumption that Microsoft are the blocker. Let's just say that it's a two-way street when it comes to communication.

Sorry, I try to err on the side of caution as well but there is no way to do that in this case. Microsoft is clearly at fault. Adding someone to a "compatibility list" is a unilateral action Microsoft took. If it works fine without being on compatibility mode, don't add it to your compatibility mode list.

If it had worked fine, it would never have been added in the first place. We don't add sites arbitrarily to the list. It's based on actual compat testing. Also every site on the list can request to be removed so if Google had tested in IE11 and discovered all was great, it's very easy for them to contact us to remove them from the list.
Post reply on HN