Why is X-UA-Compatible set to EmulateIE7? At least one widget I use with this theme renders ugly unless I change the meta tag in header.php to use IE8 rendering. As it doesn't harm backwards compatibility with IE7, why not specify IE8 instead?

header.php

<meta http-equiv="X-UA-Compatible" content="IE=IE8" />

I had the same question. I substituted IE8 based on what you wrote, and all seems well. It would be good to hear from Flynn or Juggledad if there is some reason why Atahualpa isn't set for IE8.

Originally Posted by mdmower

Why is X-UA-Compatible set to EmulateIE7? At least one widget I use with this theme renders ugly unless I change the meta tag in header.php to use IE8 rendering. As it doesn't harm backwards compatibility with IE7, why not specify IE8 instead?

header.php

<meta http-equiv="X-UA-Compatible" content="IE=IE8" />

Why not just remove the code completely, it has the same effect as changing it.

That line is there because of the problems IE8 can (and has) cause(d) with sites. With the vast number of plugins and combinations of plugins, problems in IE8 crop up )if there weren't problems, why would MS have created it?) so Atahualpa puts that line in to prevent (some of) them.

Hopefully, someday MS will release a browser that works with the same standards as the other browsers (or get out of the browser business).

However, if your site renders properly with that line removed, then remove it.

I promise not to turn this into a flame, but would like to express one point.

EmulateIE7 was introduced 2 years ago with the purpose that websites could temporarily allow their site to render as they expect in IE8. It was (and still is) expected that developers work towards making their sites IE8 compatible so the tag is no longer needed.

As developers for Wordpress plugins and themes have been working with IE8 for two years now, it seems that the default option should be for IE8 rendering, with EmulateIE7 being something that users of severely outdated plugins would need to add themselves.

EmulateIE7 actually does harm the rendering of some plugins written to be compatible with IE8, and so I'd venture to say that keeping this tag is hurting anyone who keeps their website up to date (even if only once to twice a year).

If you edit header.php, you can take it out. While I agree two years should be enough time for developers to have updated their plugins, it seems lots get abandoned, but still work and are used. And look at the number of users still using ie6 and ie7 - 17%!!!

I'll suggest to the developer, that an option be added to let you decide to remove it or not

I would like that option very much. Found out today that NGG-imageflow breaks on IE8 because of that tag.