4 ms·

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

by devx 13y ago

gbin 13y ago
but what is this setting ? it doesn't look like an UA switcher.
- randomfool 13y ago
  Compatibility view essentially switches the entire rendering stack & user agent. It even looks like the older version when inspecting many JS functions and such. I'd expect google.com to be fully standards compliant, but for some reason I believe IE was forcing itself back to IE8 mode for it. Never understood why. Even in IE8 mode though, this should have worked fine- so could be something worse (identify as IE8, execute as IE11?).
- randomfool 13y ago
  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. Furthermore, by using compat mode, the only way for google.com to use newer features in IE is to ask Microsoft to take it off the compat list then push an update to all IE browsers. In general, this compat list should die and sites should be targeting standards-compliant behavior. If they identify as standards compliant and are not, bugs should happen.
  - reybango 13y ago
    "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.
    - kumarm 13y ago
      I guess you have no way to work with a major company like Google since you are such a small organization lacking resources.
      - reybango 13y ago
        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.
        3825 13y ago
        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.
        reybango 13y ago
        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.
        joshstrange 13y ago
        What about the quote from the article: > I'll tell you more guys. I've updated to windows 8.1 on my tablet a month ago through MSND subscription and Google search worked just fine. Looks like this problem appeared after public availability of Windows 8.1. So I believe it's something that Google or Microsoft should figure out. How could they have tested as they were not on the list until, what appears to be, the public release?
        13y ago
AaronFriel 13y ago
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: <domain docMode="EmulateIE10" versionVector="10" uaString="10" featureSwitch="overrideXUACompatible:false">google.com</domain> It seems to read as: render and present as IE10, and if there is a `<meta` tag specifying x-ua-compatibility, don't ignore it. There's another section that overrides the backwards/forwards cache setting for google.com: <BFCache> ... <domain exclude="true">google.com</domain> 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.
- mbell 13y ago
  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'.
- cbr 13y ago
  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.

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

by devx 13y ago

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

gbin 13y ago

but what is this setting ? it doesn't look like an UA switcher.

randomfool 13y ago
Compatibility view essentially switches the entire rendering stack & user agent. It even looks like the older version when inspecting many JS functions and such. I'd expect google.com to be fully standards compliant, but for some reason I believe IE was forcing itself back to IE8 mode for it. Never understood why. Even in IE8 mode though, this should have worked fine- so could be something worse (identify as IE8, execute as IE11?).
randomfool 13y ago
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. Furthermore, by using compat mode, the only way for google.com to use newer features in IE is to ask Microsoft to take it off the compat list then push an update to all IE browsers. In general, this compat list should die and sites should be targeting standards-compliant behavior. If they identify as standards compliant and are not, bugs should happen.
- reybango 13y ago
  "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.
  - kumarm 13y ago
    I guess you have no way to work with a major company like Google since you are such a small organization lacking resources.
    - reybango 13y ago
      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.
      - 3825 13y ago
        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.
        reybango 13y ago
        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.
        joshstrange 13y ago
        What about the quote from the article: > I'll tell you more guys. I've updated to windows 8.1 on my tablet a month ago through MSND subscription and Google search worked just fine. Looks like this problem appeared after public availability of Windows 8.1. So I believe it's something that Google or Microsoft should figure out. How could they have tested as they were not on the list until, what appears to be, the public release?
        13y ago

AaronFriel 13y ago

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: <domain docMode="EmulateIE10" versionVector="10" uaString="10" featureSwitch="overrideXUACompatible:false">google.com</domain> It seems to read as: render and present as IE10, and if there is a `<meta` tag specifying x-ua-compatibility, don't ignore it. There's another section that overrides the backwards/forwards cache setting for google.com: <BFCache> ... <domain exclude="true">google.com</domain> 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.

mbell 13y ago
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'.
cbr 13y ago
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.