32 bit depth jpg images problem in IE when referenced locally - internet-explorer-8

We have an webbapplication that takes an image that will be uploaded and resized.
The resize-library we used saved all pictures with 32-bit depth whatever the depth was before.
We have an online client that can view the pictures via an html-file and all is fine there. All pictures are shown correctly.
The problem:
We also have an vb-winform application that download the pictures and show them in an html-file locally in an webbrowser control. But here all pictures are rejected (not rendered), just the red cross. If we create an static html-file with img-tags in them locally, its the same. All pictures that has 32-bits depth are shown as red crosses.
If we resave the pictures with 24-bits depth it magically works again. So ofcourse that was our "workaround", let the resize-library save all pictures with 24-bits depth instead.
Summary:
32-bits jpg files shows correct in IE when online but not when referenced locally in a local html-file. (This is true for IE8 on both winxp and windows7). The same local html-file opened in mozilla showed OK.
Question:
I have googled this a lot but has not found anything about this "problem". Is this a bug in IE8?

I have exactly the same problem with my own webapplication.
This isn't only a problem from IE8 but a lot of other browsers can't support the 32 bit depth on a jpg file.
For the while, no solution exist. Try to convert your picture in a 24 bit depth. Or wait for IE9.0 that comes soon. It's the only way you have.

Related

Firefox renders bad with interlaced images?

I'm converting all the images on my website to interlaced, but i found a possible issue, under OSX 10.10.5 and Firefox 38.0.5
Interlaced PNGs that are bigger than the browser window (and so they are resized in automatic by the browser) display in a very low quality, like if they are displayed in one of the intermediate layers, and not in the final version. Zooming the image to 100% removes the problem, and changing the browser windows size removes the problem as well.
Here is an example of an interlaced image:
https://trac.ffmpeg.org/attachment/ticket/161/Test_24bpp_interlaced_paeth.png
(you have to download it and open with firefox in a small window, so that the image zooms out)
This issue is happening in the 80% of the times I try the same operation.
The issue doesn't appear, instead, in jpeg progressive images.
Could you please confirm me the issue? I think it's very strange that I can't find any other people having my same problem.

No images are loading in Google Chrome - works fine in Firefox/IE

For some reason when I use Chrome to test out my website, no images load at all, not even tiny ones like loading icons or the simple "back to top of page" arrow icon at the bottom. The browser tab just hangs on the spinning circle loading state. If I refresh it like 10 times or something then a portion of the images might load. Interestingly my Nivo-Slider images never load... there is a large empty space at where the Nivo-Slider gallery should be at the top left of my page no matter how many times I refresh.
The console is completely clean of errors if you check.
Can anyone check for me why my website is not working in Chrome? It works perfectly in Firefox/IE. I admit some images might have large file sizes but it shouldn't cause Chrome to hang for like half an hour?
I'm using latest Chrome/IE/Firefox. Windows 7 64-bit.
My website: www.symphonyofpromise.com/inspiration/en
By the way my website is a completely fictional museum/gallery project, it's not the official site for some museum!
I cannot be 100% certain on this, but judging from the Network panel, you might be loading too many MP3 files at the same time, thus maxing out the number of simultaneous requests. Chrome might use a different prioritization algorithm.
I would recommend removing some of those MP3 files and deferring loading until after the initial load.
EDIT:
Nevermind that, it appears that the MP3s load fine, but other resources are definitely blocking it. A request should never be pending this long. Poke around further in the Network panel and you'll find the problem.

gif image not looping

I have created a gif in photoshop. It has two frames displayed for 4 seconds each and is on a loop forever.
For some reason the image freezes on the second frame and does not continue to load in some browsers (The exact information about browsers and / or versions is unclear at the moment but it has happened in the latest version of chrome).
The image is embedded in the code in the standard way, no javascript is used and nothing is changing the element.
Does anyone have any idea what could be causing this? Everything I have searched for so far seems to result in people saying "Oh, I forgot to put make the gif loop forever" instead of any real reasons for causing this problem.
Thank you for your help!
Edit: Sorry I didn't think about putting an image in the original post. He is an example of one advert which doesn't seem to work.
Because the current image displays correctly in everything I've tryed so far, try to create image in different application.
Some applications you may try:
GIMP - tutorial
Some freeware crap.
I'd vote for GIMP. Its complicated, but its free and it has wide user suport.
If you still fail...
Now its time to check the enviroment. First, open the image on different machine. Maybe there is something wrong with your browser instalation. In this case, reinstall.
Try to upload on different server. Maybe your browser does not correctly decompress deflated data or has other communication issues.

How does Shutterfly differentiate the two links to render images of different sizes?

I was looking at the thumbnail image in a Shutterfly rss feed and the link is
http://im1.shutterfly.com/procgtaserv/47a2d624b3127cce9854b08c5baa00000039100AYtWzNi4Yt2Qg
and this renders out a ~3KB thumbnail, as expected.
I compared it to the link to the image on the actual Shutterfly page, which has the same apparent link:
http://im1.shutterfly.com/procgtaserv/47a2d624b3127cce9854b08c5baa00000035100AYtWzNi4Yt2Qg
But when I click this link, it renders out a ~60KB image.
I've looked at this in Fiddler and Chrome Dev tools and can't see anything different in the requests that would tell the server what size to render. I've even tried copying these links into Firefox to see if it was a browser/cookie type issue but they render differently there too.
I'm driving myself crazy trying to figure out what's going on. Can anyone shed some light on this?
The two websites are different.
Thumbnail:
http://im1.shutterfly.com/procgtaserv/47a2d624b3127cce9854b08c5baa00000039100AYtWzNi4Yt2Qg
Original:
http://im1.shutterfly.com/procgtaserv/47a2d624b3127cce9854b08c5baa00000035100AYtWzNi4Yt2Qg
I opened both links in different tabs in Chrome. Then, flipped back and forth between the two tabs, staring at the URLs. There was a minor flash where the 9 changed to a 5, and vice versa.

IE not rendering png background image properly

I have create a PNG arrow graphic for use in a client's website. It render's perfectly everywhere except in IE 6,7,8 and 9. I have attached an image for you to examine and have already tried 2 different IE png fix scripts - one jquery and one a css behaviour .htc file.
Please assist me.
Thanks
Jamie
Image: http://i51.tinypic.com/2w1uzqe.jpg
Sorry to say that but for 5 years i've been looking for 100% working hack for png transparency bug in IE's with no result. There are many of them and usually each of them doesn't work here and there.
Try using transparent gif instead or crop arrow image with background along. It will take few more bytes of White color so won't damage your performance that much.
The bug that IE PNG Fix scripts are designed to fix is only a problem for IE6 and lower.. hmm.. possibly IE7? I forget. In any case, IE8 fixed the issue, and IE9 definitely shouldn't have it. These IE versions may still have plenty of bugs, but the old well known PNG background issue isn't one of them.
My guess is that there may be a corruption in the PNG file itself.
My suggestion is to try loading the PNG image into Photoshop (or your favourite graphics app), and re-save it. That may be all you need to do to solve the issue.
Failing that, would you be able to give us a link to the actual PNG file, so we can have a look as well?

Resources