So I hope Dean Hachamovitch or Jason Upton or anyone else in IE team reads this because I want to tell them, and I'm sorry for harsh words, that if I were their boss I'd fire them. Because you absolutely deserve it for not fixing the 'bmp pictures' bug.
An hour ago I've downloaded IE8 RC1 on 32 bit Vista Business with SP1, fully updated and what bothers me is a bug that was partially responsible for me switching to an alternative browser. When you right click on picture and select 'Save As Picture' the only
available format is bmp file.
This bug cannot be always reproduced, it's affected by header information that comes with picture, but personally I can always reproduce this bug on
this site. I've looked for a solution on internet, but it seems they are all written for older versions of either IE or OS - deleting temporary files doesn't work and it's not possible to empty 'Downloaded Program
Files' folder under Vista as is suggested in
KB article.
Now I've done some research (read googling) and it seems the error is caused because IE sometimes (I guess probably for perfomance reasons - to save memory in ram) discards original format and keeps only bitmap representation that is convenient beacause this
is format that can be displayed with the least amout of cpu processing. I'm fine with that, but why couldn't you redownload image when user selects 'Save As Picture' menu - or at least convert it back into original format if resending picture file is not
possible. If you click 'Properties' on that same menu, IE reports original format (so IE certainly has some knowledge about format of original format), so why not convert it back - I don't really mind artifacts that will come with encoding back bitmap to original lossy
format (like jpg).
I can't stand BMP files on my disk - you may think it's good enough, it gives you few megabytes smaller memory footprint (but you already eat tens of megabytes), problem is everybody else does it correctly - Firefox, Opera, Chrome and others.
You could say I'm a bit of ms fanboy, you don't see me using that tone often - but really - it's either you are doing this intentionally and aiming for cheap way to lose few megabytes in memory with too aggreessive cache regime , or - and there is argument
for this, you are not doing this on purpose and are just too incompetent to fix this bug that, according to previously mentioned
KB article, has been plaguing IE since July 2000 - when IE 5.5 was released. 8 years.
Again sorry for angry words, but it's about time you fix this bug - otherwise IE is great, I love accelerators.