IE9 + generated content in image source bug

[desandro]

IE9 + generated content in image source bug

[desandro]

Thanks so much for going into depth about this. I'm sure others are running into this often and just haven't spoken up yet. Could I ask you to post your solution code for this problem?

[justinhillsjohnson]

Hey guys, I'm also having an issue with cached images not firing the handler passed to .imagesLoaded(). We're also using a CDN but the asset path doesn't have a query parameter appended to it. Pull request #9 did not fix the problem. From experience, typeof elem === "undefined" is the same as elem === undefined.

I'll report back if I find a solve.

[justinhillsjohnson]

If I eliminate the conditional @ line 43, then the script no longer fails in IE9. One thought I have is to pass in a 2nd optional parameter that can be used to enter into the conditional @ line 43. Something like if (this.complete == || typeof this.complete === "undefined" || purge) { ... }. Then, when I instantiate the plugin, I can pass the handler and purge == true || false. For example:

$('#id').imagesLoaded(handler, $(document.body).hasClass('ie9'));

[desandro]

This should be resolved by #11

[justinhillsjohnson]

Interesting, #11 didn't fix it my particular problem with images showing as broken in Win7 IE9. http://cl.ly/2l3R0H3z0W1p2x2l2Y26

It's highly likely this is a PEBKAC error, given that others have confirmed their IE9 problems are resolved.