Samples use X-UA-Compatible IE=7, IE=9, IE=10

[Anonymous User]

Original User: mmoles

After a bunch of reading on how that works, it pretty much tells IE8 to render using IE7.

So, my question is... why?  Is there a problem with IE8?  


Edit:  Well, I was testing this a bit, and it turns out, adding IE=8 to the list did absolutely nothing.  It still loaded in IE7 Doc mode.

This is basically what i decided to go with.
<meta http-equiv="X-UA-Compatible" content="IE=10,chrome=1">

[Anonymous User]

Original User: evtguy

I can think of one thing that sucks with IE-8: dojo charting.

Microsoft, in their infinite "wisdom", suddenly changed the graphics renderer in IE-8 so any dojo based charting that is in your application won't work without altering the dojoConfig options (and even then it's not a guarantee that it will work).

[Anonymous User]

Original User: mmoles

If i am using jsapi 3.6 , then it should be fine right?  The baseline that i need to work is IE8.  I may be able to convince some people to allow us to use chrome frame.

[SteveCole]

The latest API version doesn't necessarily mean things will work in IE-8. All versions of IE before v9 are notorious for being NON-standards compliant which makes life a living hell for web developers. In my organization, IE-8 is still the default browser so I did have to ensure my application would work under IE-8. I ultimately switched my charting from a Dojo solution to another solution 3rd party solution because I could not get it to work under IE-8. Everything else worked fine- just not my charting.

So- will v3.6 work? Probably, even most likely. You asked why someone would avoid IE-8 mode and this was one reason from my experience.

[Anonymous User]

Original User: mmoles

Cool, thanks for the info.