IE8 Compatibility View

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View
IE8 has a Compatibility View button to the left of the refresh button,
which I do not want to see active for my website. Some googling shows;

and /

which suggest including;

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

in the HTML source. When I do include the above meta tag, the
compatibility view button disappears.

Questions; is there a site wide method of defining the UA
compatibility without having to specify it in every single HTML file?
No? Which version of IE should I be compatible with? Should I say to
the user "you must run IE8 in order to browse this site"?

Are there similar specifiers for Firefox and other browsers?

Essentially, can someone explain this to me comprehensibly? I wish to
let the user browse with IE8 or FF3.6 with as little pain in terms of
meta tag coding as possible.

What happens if I specify IE8 and the user has IE7 or (horror) IE6?
Does the browser ignore the specifier?

Re: IE8 Compatibility View

 npx@no.spam wrote:

Quoted text here. Click to load it

It is not much to specify but you could use an include instead.
And make it count more by putting in this include any other thing
you tend to repeat in the head sections.


Re: IE8 Compatibility View

Quoted text here. Click to load it

You should be compatible with HTML standards.

Quoted text here. Click to load it

Only if you don't care about pissing off the visitors to your side. Many
visitors who use other browsers would see that, leave, and not come back.
Quoted text here. Click to load it

No, because this isn't a problem with standards-compliant browsers. It's a
problem only with IE.
Quoted text here. Click to load it

Then code for compliance with standards. Do all your development using a
standards-compliant browser such as FF3.x, Opera, or Safari. Once the site is
functioning properly in standards-compliant browsers, test it in IE and make
whatever IE-specific tweaks or hacks are necessary to make it behave the same
in IE as it does in other browsers. If you do it the other way around --
design for IE first, then try to make it work with other browsers -- you're
buying yourself a whole lotta nuisance.
Quoted text here. Click to load it


Re: IE8 Compatibility View

On 06 Apr 2010, npx@no.spam wrote:

Quoted text here. Click to load it

What if a user only has ie7 or even ie6?  Are you saying you don't want
any such visitors to view your page?  If so, use conditional comments
(or arguably server-side scripting) to prevent those users from viewing
your page.  If not, what you *are* doing is a complete waste of time.

Quoted text here. Click to load it

Neredbojias /

Re: IE8 Compatibility View

On 4/6/10 12:20 PM, npx@no.spam wrote:
Quoted text here. Click to load it

I have to agree with those who say "Forget it!"  Don't create Web pages
with a particular browser in mind.

Compose a page, using any browser to observe the draft.  Test the
through < ; if you use CSS (and you should),
test that through < .  Fix any errors
that are indicated by those two validators.  Then review the results
with a Gecko-based browser (Firefox, SeaMonkey, etc) and another modern
browser (Chrome, Safari, IE 7 or 8, etc).

No, you can't get the page to look exactly the same with all browsers.
But if something is totally awry, adjust it, retest it, and look at it
again with two browsers.

Note:  The last time I checked, IE 8 had more users than either IE 7 or
IE 6.  But IE 7 and IE 6 together had more users than IE 8.  Also, all
versions of IE combined were used by 35% to 50% of those who surfed the
Web.  In other words, 50% to 65% of those visiting your Web site might
not be using any version of IE.


David E. Ross
< .

Anyone who thinks government owns a monopoly on inefficient, obstructive
bureaucracy has obviously never worked for a large corporation. 1997

Re: IE8 Compatibility View

On 6 apr, 21:20, n...@no.spam wrote:
Quoted text here. Click to load it

What happens in five years when you want to use features supported by

I would go for

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

Site Timeline