That is quite odd. The only thing that comes to mind is to make sure that the image file is actually a .jpg. Lazy programs will try to render an image based primarily on its given extension, but smarter programs will read the binary header info and judge what type of image it is. Its possible that the image in question is not a .jpg, but it just has the .jpg extension. Thus ff is looking at the file header and seeing its not a .jpg and transcoding the file in realtime (and so you'll also get a .jpg file if you save it from within firefox), while ie may just be looking at the extension and judges that it is a .jpg and thus fails to render it. Hopefully that makes sense ;-)
It renders without problems in Safari and Opera as well.
Looking at the image info in FF, FF says it is an image with type JPEG and mime type images/jpeg.
I suspect that there is something in the header info of the jpg that IE doesn't like as a result of how the image was originally created.. Opening the jpg in something like Photoshop and resaving it as a Photoshop generated jpg should fix any header problems.
I suspect that there is something in the header info of the jpg that IE doesn't like as a result of how the image was originally created.. Opening the jpg in something like Photoshop and resaving it as a Photoshop generated jpg should fix any header problems.
During loading the image into Photoshop Elements, it asks me to convert the image to a supported color mode: rgb, grey scale, index or bitmap.
Reply With Quote
Originally Posted by tracknut
Bookmarks