Web Browsers - The CSS - page 27

<meta http-equiv=”X-UA-Compatible” content=” IE=8 ” />
The next example tells the browser to emulate IE7 and use the DOCTYPE
derived mode:
<meta http-equiv=”X-UA-Compatible” content=” IE=EmulateIE7 ” >
More background and examples of values for X-UA-Compatible are
available from Microsoft ( http://msdn.microsoft.com/en-us/library/
cc288325(VS.85).aspx ).
Specific Mode Differences
If you want to know more (and aren't content to just ignore that Quirks
Mode exists at all), Jukka Korpela has a very detailed list of differences
between Quirks Mode and Standards Mode in various browsers ( http://
www.cs.tut.fi/~jkorpela/quirks-mode.html ). Peter-Paul Koch charted many
of the differences in an easy-to-read table ( http://www.quirksmode.org/
css/quirksmode.html ).
Targeting Browsers
In a perfect world, there would be no need to send or hide specific styles
to specific browsers or find ways to accomplish something without CSS
that there are clearly defined properties for. In the real world, you can get
away with being almost perfect. Under Standards Mode rendering, send-
ing different style rules to different browsers is not the norm, but some
projects will require a small tweak here or there to pull a stray browser
back into line.
Here I show three common ways to approach browser targeting and why
they work. The first two are useful if you need to make minor changes,
and the last is useful if you are making more regular changes, particu-
larly if you have to develop for older versions of Internet Explorer.