IE8 display issues

So, I'm sure this is not news to anyone: IE8 cant render an Echo2 application properly. So, I came across this little tidbit on wikipedia:

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

This meta tag will force IE8 to operate in IE7 mode. The question is, how can I make it so that it is included in the HTML sent back by Echo2?

Thx

Pierre

I can only agree with you.

I can only agree with you.
Echo3 is still beta, and converting an existing echo2 app to echo3 is not a one day job.
So echo2 should work with IE8.

Olaf

tliebeck's picture

Yes Echo2 should work with

Yes Echo2 should work with IE8.

I just fixed a bug with background images being displayed incorrectly, was that the issue you were encountering? Re-ran the nightly builds as well.

I'd prefer not to force IE7 emulation if possible. But you can modify WindowHtmlService to produce the meta tag if absolutely required.

Is the main problem here in some specific component, and if so, what component?

Yes, the main issue is the

Yes, the main issue is the background images. They are either not displayed, or displayed "off". Where can I get my hands on that fix? I keep a version of the code locally and apply fixes manually, so, a link to the code to paste in would be grand.

Thx

Pierre

a.schild's picture

Nightly build can be found

Nightly build can be found here: http://download.nextapp.com/downloads/echo2go/

If you maintain your own version, then working with SVN would probably be a good idea.
The echo2 source should be available here: svn://svn.nextapp.com/echo2

Got the latest build,

Got the latest build, deployed, works perfectly now. Rock and Roll!

Pierre

We had an IE8 issue with an

We had an IE8 issue with an external stylesheet file within an "echopointng.TemplatePanel" .
After integrating the stylesheets into the html-Template it works.

What about a new release?

Yes, the nightly build solves my IE8 issues too (the title bar of SpWindowPane was broken).
What about officially releasing this build? Actually the latest production build doesn't support IE8 (not well, at least: I have had to use the compatibility mode). So people get v2.1.1 and then need to move to the nightly build (if they find this thread).

Pino