@jmbucknall no, that bug is new to IE8. Switching to IE7 rendering mode "fixes" it. Try it yourself on so.com