New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Image is loaded twice #67
Comments
I don't think that IE9 is old enough to drop it's support but yes multiple requests are the bad thing. One solution is to run this loader only in case of old browsers and use normal loader otherwise. |
Hi @can3p, I have very huge images(like >30MB) to display using the plugin. Multiple requests would make my application really slow. And also, since "loaded" is called from inside onload callback for "img", for heavy images, the onFinishLoad is triggered even before the "self._img[0].src" actually loads. Do we have a fix for this yet? In the above code, i tried to invoke "loaded" in onload callback for self._img[0] and it works, but i don think its the right way to fix it. Can you look into the same? |
@mridula-tripathi Are you able to reproduce this bug? I thought I could do it before, but yesterday I checked the test page in both Google Chrome (Stable, Unstable), Firefox (Nighly) and IE 11 and I don't see any duplicated requests for images. If you can reproduce the bug, could you please post a step-by-step guide for it? |
Still happens in Chromium version To reproduce just open index.html, and click on the But yeah, maybe this is a chromium bug because it is a fairly old version on ubuntu 12.04. |
I too tend to think that this behaviour is fixed. Could you test on a latest version of Chrome? |
@mridula-tripathi I've accepted your pull request and refactored it. Please, test and tell if the issue is fixed. |
Yep, looks good now. |
This is visible on
index.html
when you clickChange image
and you make your browser show you network requests.It is because of:
I understand there are some hacks around IE8/IE9, but I think double loading the image is a serious performance issue. Wouldn't it simpler to drop IE < 11 support? :)
The text was updated successfully, but these errors were encountered: