Hi Eric, thanks for your reply.
"Using jQuery to backload any additional plugins or scripts can be super useful" - yes, that's why I've been doing for a while now. :) As mentioned, I was primarily playing around with these techniques to see how it goes, and I wish I could have a gotten a bit more info on why it doesn't seem to work properly in IE (more than an unknown error at least). I think if there is a recognizable increase in performance then for rather "massive" pages. So I actually don't need to worry about this too much... ;) Cheers On 6 Aug., 23:03, Eric Garside <gars...@gmail.com> wrote: > Honestly, I'd load jQuery regularly, and use the getScript function to > load the rest of the files after domready. I don't know that you're > getting a big performance increase in loading the jquery library in > this method, and it is causing an unknown error, which isn't an ideal > thing to debug. :P > > Using jQuery to backload any additional plugins or scripts can be > super useful, but including the jQuery library asynchronously seems > like a poor decision. > > On Aug 6, 4:12 am, north <ollo...@web.de> wrote: > > > Hi all, > > > I played around with Steve Souders' techniques of loading JS without > > blocking a bit (I had already been using jQuery's getScript/ajax to > > load bigger chunks of code for certain parts of the site only if > > necessary). > > I tried to use what Nicolas Zakas calls "the best way to load > > JS" (http://www.nczonline.net/blog/2009/07/28/the-best-way-to-load- > > external-javascript/) for the project I work on. > > > I created the <script...> tag for jquery.js the way described in the > > article, and then tried to use onload/readystate to start loading the > > file with my plugins/functions right after jquery did. > > > This seems to work fine in all browsers except, you guessed it, IE... > > For some reason IE (I think it happened in 6, 7 and 8) throws me an > > unknown error every now and then. > > It's just a guess, since an "unknown error" doesn't really help me > > debugging, but maybe sometimes the plugin/functions file finishes > > loading before jquery. Even though that should be prevented by > > checking the readystate... > > > I tried several other approaches then (like adding an ajax call to the > > plugins/functions file at the end of the jquery file, or checking for > > (typeof jQuery == 'undefined') in a loop to try loading the files as > > soon as this statement equals false), but none would work. > > > Is anybody using one of these non-blocking techniques with jQuery > > successfully? > > > Thanks
