Internet Explorer 8 released

The fabled, IE8 is here ushering in a new era of compatibility, Web standards and fewer browser bugs. There will be much rejoicing by Web developers whose jobs will suddenly become easier and they can spend more of their time creating great Web sites that make the world a better place.

Not quite.

Compatibility in IE8

In a post on the IEBlog, Just The Facts: Recap of Compatibility View, IE8’s compatibility is explained. Be sure to take some notes because simple it ain’t. Yes, IE8 runs in standards mode by default, but the new “Compatibility View” feature and IE8 site blacklist start making things difficult.

Since the IEBlog is about as clear as mud, I found an alternative explanation on the topic, The IE8 Blacklist minefield. I suggest giving it a read. It clearly explains the situation and what Web developers have to do about it.

What are the issues with IE8?

To sum it up quickly, here are the things you should know about IE8 and compatibility:

• IE8 renders in standards mode by default unless
  • Your site is on the IE8 blacklist
  • A user opts to run your site in Compatibly View
• Compatibly View does not render the same as IE7, so you have a new browser to test in (yay!)
• You can select which mode the browser renders in by using a versioning meta tag or HTTP header
• If you use select a rendering mode, your site visitor will not have the option to use Compatibly View

So basically, I have to opt-in to standards mode?

Yup. The IE8 blacklist basically forces you to pick a rendering mode or else Microsoft or your users will pick for you. That’s the only way a developer will have control over how their content is rendered.

Start learning those meta tags and start testing.