James Leslie wrote:
Using <meta http-equiv="X-UA-Compatible" content="IE=8" /> will also
have the same effect (getting rid of the compatibility view button
and forcing standards mode), but may be a bit more stable against
future releases of IE.
But, may also lock documents to IE8's rendering capabilities even if
future IE releases can handle more, better - which they should. Not very
wise, IMO. You wouldn't choose/advice such a "safeguard" strategy for
any of the other browsers, would you?
IE8 does have a few dozen irritating bugs and weaknesses, and is (pretty
much) limited to CSS2.1. However, IE8 final is pretty stable and works
quite well for all properly built sites, so one can say Microsoft has
done an acceptable job. No signs they'll jump off the "standards path"
either now that they've finally got on it, even if they're a little
behind the others.
What's holding IE8 back now is all those sites that has been
"safeguarded" and tailored to work in earlier IE versions as if there
was no tomorrow, and it is about time we stop treating IE as a browser
that will be in need of special solutions forever.
Georg
--
http://www.gunlaug.no
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
*******************************************************************
