Hello,

Adaptative theme uses meta tag for IE compatibility (Chrome too) : <meta http-equiv="X-UA-Compatible" content="IE=edge, chrome=1">
But, in intranet sites, this meta seems not to be recognized correctly.
According this blog, and other articles in MSDN, this meta tag should be the first one ! It works on my intranet.
So, should it be possible to sort differently the meta tags in the html.tpl.php file like this ? What do you think about that ?

<meta http-equiv="X-UA-Compatible" content="IE=edge, chrome=1">
<?php print $head; ?>
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="MobileOptimized" content="width">
<meta name="HandheldFriendly" content="true">
<meta name="apple-mobile-web-app-capable" content="yes">
<meta http-equiv="cleartype" content="on">

Comments

Jeff Burnz’s picture

Jeff Burnz CreditAttribution: Jeff Burnz commented
Category: feature » task

In 7.x-3.x this would be possible, to sort them, in 7.x-2.x if its meant to be first (cant say I am the worlds greatest expert on this), then we can just move it there. Is there a real need to be able to sort them, if it needs to be first then we just make it first?

Jeff Burnz’s picture

Jeff Burnz CreditAttribution: Jeff Burnz commented
Component: CSS/HTML » Documentation

OK, well according to the blog post linked to:

  1. The X-UA-Compatible meta element must be the first meta element in the head section.
  2. You cannot have condtional IE statements before the X-UA-Compatible meta element.

The second of those things makes this a documentation issue, because this theme uses conditional comments above the X-UA-Compatible meta element, in both 7.x-2 and 7.x-3 versions. I am not sure how to fix that in the theme via automagical means, I could provide a theme setting for it, but... its more UI complexity for what is, in essence, an edge case.

In 7.x-2.x this is a doddle to work around because you can just edit html.tpl.php and set it up how you need, in 7.x-3 its not so hard either, you can also edit html.tpl.php and add the X-UA-Compatible meta tag manually and not use the theme setting to enable it.

Jeff Burnz’s picture

Jeff Burnz CreditAttribution: Jeff Burnz commented
Title: Activate IE compatibility mode » Avoiding Smart compatibility with X-UA-Compatible in IE9 on Intranet Sites

Changing to more accurate title.

Jeff Burnz’s picture

Jeff Burnz CreditAttribution: Jeff Burnz commented
Version: 7.x-2.2 » 7.x-3.x-dev
Status: Active » Closed (works as designed)

Really this is a closed "Cant fix", due to the themes use of conditional classes on the html element. The fix would be to override html.tpl.php and remove those classes, however, watch out, they are used by the responsive system to provide styles to older versions of IE (IE7).

I will check the metatags are loading first, that would be harder to fix due to the theme know using adaptivetheme_html_head_alter() to inject its metatags.

Ops, just checked, they are not first, so will update so they are.

You can also turn any metatag OFF in the theme settings now.

m-patate’s picture

m-patate CreditAttribution: m-patate commented

Thanks a lot Jeff for all your efforts & consideration to this issue.
I will still use finally this tag moved manually in the template file, I understand it's not so easy.
Nevertheless, AdaptativeTheme rocks ! (+Sky)

Jeff Burnz’s picture

Jeff Burnz CreditAttribution: Jeff Burnz commented

You will be safe if no one is using IE7 or below, that is the only thing I use the conditional classes for in AT Core. Even then, its not a huge big deal, occasionally a region might be wrapped below, that is all, so the layout might be slightly broken on these older browsers.

ShaneOnABike’s picture

ShaneOnABike CreditAttribution: ShaneOnABike commented
Issue summary: View changes

Could we document this somewhere because it's fairly important and I did not see any settings in adaptivethemes for this.... So frustrating IE sometimes eeesh