On 9-Dec-09, at 1:55 PM, Lex Spoon wrote: > On Wed, Dec 9, 2009 at 12:47 PM, Matt Mastracci > <matt...@mastracci.com> wrote: >> Do you know how to get onerror to fire in IE? It didn't seem to >> work in my >> testing. > > No, but why do you need it if you have onreadystatechanged? It should > be no problem to hook up both callbacks.
Yeah, you don't need the onerror stuff in the end - everything can be done via onload and onreadystatechange. I was hoping that one of the browsers would justify adding onerror to the mix by providing some additional information on why the script failed to load, but there's nothing useful in any of the errors that I've seen. Setting up both onload and onreadystatechanged, directly assigned to the properties on the script element's DOM object seems to be the way to go. It covers both the success and error cases and works on everything but Opera. Matt. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
