Disabling IE8 compatibility mode, good or bad?

I hope this question is not as subjective as I think it might be.

I have an Intranet application that should work with IE8 as the enterprise replaces IE6 as a standard browser.

Our testing team found that it did not work in IE8, few people knew that this was really so. Their browsers were configured to run IE8 in compatibility mode for Intranet applications.

I found that if I set the meta tag for X-UA-Compatible for IE = EmulateIE8, I could make the browser display this application as IE8, and the application worked fine.

Are there any pitfalls that I do not know about this decision? If so, is there a better solution?

+5
source share
1 answer

Configuring X-UA-compatible with IE = EmulateIE8 will force future IE9 to behave like IE8.

Initially, this could be what you want. If you can’t fully test against IE9 when it appears (sometimes next year, I suppose), it can help if the organization immediately switches to IE9.

When you have fully tested everything and want the application to run in IE9 native mode, you are a little stuck. You can install X-UA-compatible IE = IE9, and IE9 will work fine, but what does this mean for IE8?

This is all speculative. Now it will not hurt anything. If you need to make changes to handle later versions of IE9, you can do this later.

+5
source

All Articles