More findings from IE8: XHTML and @import

Warning This article was written over six months ago, and may contain outdated information.

Had the chance to run a few more tests to find out what’s new (and what’s not) in IE8. Good: @import media types seem to be imple­ment­ed; Bad: XHTML still isn’t parsed, so every­one who thinks they are cod­ing XHTML are still kid­ding themselves.

4 comments on
“More findings from IE8: XHTML and @import”

  1. Hmm, although it’s a step in the right direc­tion that they’ve includ­ed sup­port for @import media types, I’d like to see Media Query sup­port by the time it becomes an RC, bring­ing it in line with Safari, Opera & hope­ful­ly FF3 (no sup­port as of yet)

  2. Looks like it’s time to give up try­ing to sup­port IE once and for all. I’ve wait­ed 3 major ver­sions for ms to get their act togeth­er but even there lat­est beta brows­er is STILL inca­pable of even basic XHTML ren­der­ing which all oth­er well-known browsers have had work­ing for over half a decade now.

  3. Give up sup­port­ing IE?

    Tell that to the almost 90% of peo­ple that still uses that POS brows­er. If you don’t sup­port IE, they won’t switch. They just won’t vis­it your site.

    I’ve already giv­en up sup­port­ing IE6, which is an absolute web design­er’s night­mare. But we’ll still have to sup­port IE7 and IE8, unfor­tu­nate­ly, since it’s still the most wide­ly used browser.

  4. FYI, there will be no sup­port for Print media descrip­tor when used in con­junc­tion with the @import rule, in the final ver­sion of IE8