Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.



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.


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'.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: