Actually anything which is newer than 1997 is problematic for IE... and Microsoft was/is unwilling to fix those problems until the s**** really hits the fans, which for Microsoft means, the users run away, not thatThe only fix that I am aware of is to use a style to apply to the image.
Actually no there have been several javascript fixes floating on the web for years...
I didn't mean to imply there were no other fixes. I was just saying that was the only one I knew about so that was all I could comment on. ;-)
the damage costs by lost man hour of others due to their unwillingness to fix the flaws can be counted in billions.
The Ie is not the only program with long term problems where the developers only give back the standard message, we have no budget and are not allowed to fix those things.
Outlook Express, or lets say, the nntp part of that program also has
several severe issues which have been open since stoneage which break the usenet specs significantly.
People already have written proxies to bring things into order.
Unfortunately a proxy is not a solution for a broken rendering engine.
I just checked the stuff the gui does who runs the IE7 CSS fixing project. This guy does an amazing job by bypassing bugs and plugging missing tags into the IE rendering engine.
It seems he has driven this stuff so far that you finally can start to use CSS positioning on a serious scale (which basically was broken because Microsoft never has fixed the bugs in several related tags, which broke positioning and font size handling on a serious scale.
(No wonder, a working cross platform CSS positioning is a important step to a browser based cross platform desktop or at least neutral very good cross platform content rendering, things the Microsoft management hates)
Some of those fixes work because people found loopholes or other bugs which could be exploited to touch the correct functions in the IE engine. Which means some of the missing functionality is there but it simply is turned off or hidden.
