additions...

…web design…

approach IE8 betas with caution…

IE8b1 isn't a real beta – rather a late alpha, so it would be nonsense to introduce major changes to any CSS based layout based on what shows up in that version. However, IE8b1 can be used to check and refine existing strategies for making IE7 and older IE versions behave, so we do not inadvertently hack IE8 too. IE8 final is supposed to not be in need of any hacks.

IE8b1 offers pretty broken support for the remainder of CSS 2.1 – the parts that was left out in IE7, and the additional support for bits from CSS 3 is not worth all that much yet.

A few serious bugs related to CSS properties/values that worked just fine in older versions, turns even the thought of making adjustments for IE8b1 into a pretty nonsensical exercise in most cases.

So, there are lots of CSS properties/values that IE8 is supposed to support, but which the early betas either handle pretty buggy or not at all – yet. This will definitely improve before the IE8 final is released, so seeing something break in an IE8 beta is no big deal – unless of course if it breaks in the better browsers too.

design for better browsers…

The safe old strategy of designing for better browsers first and fixing IE/win later, is still by far the best strategy – and the only strategy I can recommend. If IE8b1 renders a creation ok, then fine. If not, then make notes and carry on.

Designers who know the relevant specs well enough to rely on them instead of what's rendered in individual browsers, can of course do a lot based on how things are rendered in early IE8 betas compared with better browsers, while waiting for IE8 final to arrive with its “best possible standard” support. I'm personally pretty confident in this respect, so I make “safe” adjustments to avoid some of the CSS properties/values that I can see IE8b1 is having serious problems with – but only when I'm pretty sure those adjustments won't come back to haunt me in a properly working IE8 final as well as in better browsers.

check bug-reports, report new bugs and wait…

That headline says most of what less experienced web designers should do when they encounter something that doesn't look right in an IE8 beta – or any other software beta. Doing much more than that is more like gambling.

I think I'll leave it there for now, and go through some of the many test-cases I have on site to see what IE8b1 makes of them.

sincerely  georg; sign

Hageland 19.mar.2008
last rev: 19.mar.2008

additions...

If IE8b1 renders a creation ok, then fine. If not, then make notes and carry on.
— Georg

Forget all about the “version targeting” introduced in IE8. Only really huge IE/win-only sites that are completely beyond normal rescue-operations, will ever need such a “solution”.
— Georg


about…
…2008