Home/ Questions/Q 6471079
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T06:11:01+00:00

let’s assume I have a so called 2.0 app, compatible from IE6 upwards. The

  • 0

let’s assume I have a so called 2.0 app, compatible from IE6 upwards. The app uses quite complex CSS and is driven by heaps of JS. It works, very well it does.

Now let’s assume there is a client who own a strangely coded site, archaic in ways, and forces IE7 emulation through this wonder of a tag:

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

Now, he desires to use my app, which is injected in his code using a simple external script call. It works, but not so under the IE7 emulation – obscure bugs from Hell start appearing, not even overflow hidden works properly. By itself the app does work in IE7, but as it turns out, the IE7 emulation is not the same as IE7 and has it’s own set of fancy issues.

Turns out the client is unable to strip the emulation meta tag, so I’m left with I don’t really know. Does anyone know of ANY WAY I could overpower the rendering mode set in the page header or would there be some other suggestions?

My utmost thanks for anything usable.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Perhaps you could make a wrapper for your app. An iframe that contains an empty page to make the script call. The content of the iframe should not be affected as the meta won’t be present in the empty page.

    • 0