Home/ Questions/Q 6126609
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T16:23:49+00:00

<meta http-equiv=X-UA-Compatible content=IE=edge,chrome=1> This is a very cool piece of code that forces Chromeframe

  • 0
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">

This is a very cool piece of code that forces Chromeframe or latest rendering engine. It can even be sent throught the http headers if you want the html to validate. But with this comes a doubt for me. I use IE8 in compatibility mode to test my websites for IE7 (either clicking the “sheet-of-paper” icon next to the URL box, or by activating “browsing mode” in developer tools). So my question is:

Does compatibility mode still renders webpages as IE7, or does the X-UA instruction blocks my intention?

Im worrying that I think ive checked my pages in IE7 and it turns out what im seeing it’s not really what a native IE7 would show….

Thanks for your comments.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Anything you do in developer tools overrides the headers and meta tags. Here’s a flowchart which explains it all:

    IE Compatibility view flochart

    • 0