Ticket #3637 (closed bug)
Local scripts loaded using getScript isn't available (directly) in Firefox 3
| Reported by: | sandstrom | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 1.3 |
| Component: | ajax | Version: | 1.2.6 |
| Keywords: | firefox, getscript | Cc: | sandstrom |
| Blocking: | Blocked by: |
Description
Local scripts loaded using getScript isn't available (directly) in Firefox 3.
See these three threads for discussions on the problem:
http://groups.google.com/group/jquery-en/browse_thread/thread/a1c82c2226f781 http://www.nabble.com/$.getScript-in-Firefox-3-td18108981s27240.html http://www.henrytapia.com/archives/2008/04/22/load-only-the-jquery-plugins-you-need-when-you-need-them/ (at the end)
this is one way of fixing the problem $.getScript = function(url, callback){
if ($.browser.mozilla) {
var _callback = callback; callback = function () {
setTimeout(function(){
_callback();
}, 50);
};
}
$.ajax({
type: "GET", url: url, success: callback, dataType: "script", cache: cache
});
};
Change History
comment:2 Changed 4 years ago by dmethvin
Another thought: if this is a race condition of some kind (onload event firing while the script is still being evaluated), it might help to try loading a very large test script.
comment:3 Changed 4 years ago by drawrof
Just wanted to note that this still occurs in Jquery 1.3.2. A fix is available in one of the links that the OP posted, which basically amounts to forcing all $.getScript requests to be processed as if they were cross-domain requests.
comment:4 Changed 3 years ago by snover
- Status changed from new to pending
This ticket has been marked as missing a test case. In an effort to reduce the number of outstanding tickets in the bug tracker, it will be closed automatically in 30 days. In order to prevent this from happening, please provide a working test case. If a test case has already been provided and our records are wrong, please respond to the ticket so that it can be fixed. Thank you!
Please follow the bug reporting guidlines and use jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.

Ok, I read the article. Nothing close to a solution is presented. The best we can do is keep that article alive and get to a fix.
We need, at least, a minimalistic test case to reproduce the problem.