jQuery Forum

When you say 'onload' do you mean document ready? Right now the require code only intentionally delays the ready event (which should work in Chrome).

I mean't onload.  I was trying to write some tests for it using qUnit.  Because qUnit waits for onload before running its tests, it fails.

I haven't looked over the code with your response in mind, but I am guessing if I used addEventListener to DOMContentLoaded Chrome wouldn't work?  I'm guessing the ready event is know DOMContentLoaded and all scripts have loaded?

My guess is because if onload fires before the scripts are loaded, there's no way that DOMContentLoaded fires before the scripts are loaded.

Of course I am seldom right.  I will explore later tonight.

Thanks for your response.   I should be clearer about what I am talking about.

I think that the script loader should, if possible, delay the native browser events.  In my experience w/ JMVC's loader, people want to use it to load a lot of 3rd party (non-jquery) scripts that depend on listening to load or DOMContentLoaded.  They will be confused when they suddenly stop working in Webkit.

 qUnit is an example of this problem, but there are lots of non-jQuery scripts that will share this problem.  I'm not sure if working with non-jQuery scripts is a concern, but having things happen in a different order depending on browser might be concerning.  My guess is that you'd rather have ready just know about DOMContentLoaded and have $.require be independent.

I've solved this by using document.write in webkit.  But write is considered evil, and I don't know a great way to pick the method w/o browser sniffing.