Hey, Matt, I've now double checked on several browsers other than Opera, and I agree that onerror works on non-IE and onreadystatechange works on IE. Details here:
http://blog.lexspoon.org/2009/12/detecting-download-failures-with-script.html One tricky aspect is that I don't see how to get IE to say whether or not the download really failed. Sometimes the "loaded" state is reached when loading a page that is not in cache. Ideas would be welcome about how to deal with that. In the experiments I did, the callback always happens after the script evaluation. If that sequencing is reliable, then it will work to always call the on-failed handler but to have AsyncFragmentLoader quietly ignore such calls if the fragment has already loaded successfully. It tracks the already-loaded fragments anyway, these days, so this would be easy to do. As a bonus, always calling, whether in state "loaded" or "complete", would give good handling to situations where the browser downloads *some* content but it's not the real JS code, e.g. the "please log in" pages that hotel wifi networks insert. Lex -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
