Actually not all of us work on ClientAPI assuming (without looking into too much detail) that this is actually a ClientAPI issue, and those who work on ClientAPI are probably busy doing other stuff (maybe to feed their mouths), and if there is an issue and nobody has logged a bug in support.dotnetnuke.com (can anybody point to an outstanding issue? NB the issue is quoted is not an outstanding issue and is different - "auto" was not considered) then it probably won't ever get fixed, and sometimes bugs don't get fixed because there simply aren't enough resources or we too are busy...

Then again IE8 has barely been out for barely a month and this is a new IE8 behaviour...

Old bugs resurface all the time (nb note this is a similar but not an old bug), often because of other code changes, and the way to squash them is to help out rather than stand along the sidelines and point.

Simple as that I'm afraid... I very much appreciate the feedback on this forum (many thanks Rytis) but the issue needs to be logged in order for it to get somewhere. It gets nowhere if you simply just jump up and down and shout "fix it " here :).

I am impressed by the DotNetNuke Corp's marketing strategy.