Side navigation
#1768 closed bug (duplicate)
Opened October 01, 2007 09:35PM UTC
Closed November 12, 2009 03:06PM UTC
$.getScript() never fails on load
| Reported by: | digitalspaghetti | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 1.4 |
| Component: | ajax | Version: | 1.3.2 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
$pastemonkey('#recaptcha_div').livequery(function(){
var self = this;
$pastemonkey.getScript('http://notapi.recaptcha.net/js/recaptcha_ajax.js', function(){
setTimeout(function(){
if (typeof Recaptcha != 'undefined') {
Recaptcha.create("6LfncwAAAAAAAIxurXazJ0zspoEwBpeVUfNr87Hr", self);
} else {
$pastemonkey.unblockUI();
};
}, '5000');
});
});
Above is a workaround that I tried, that still always fails, the reason is the URL above is wrong, so the getScript should fail, however it never fails, so the unblockUI is never called, this freezes up my UI.
A suggestion to fix this is to pass in a timeout and a fail callback into the getScript function, something like:
.getScript('url',timeoutVal,successCallback,failCallback)
If the script is not recived within the timeoutVal, fire the failCallback otherwise successCallback
Attachments (2)
Change History (5)
Changed December 06, 2007 08:23PM UTC by comment:1
| component: | core → ajax |
|---|
Changed December 14, 2007 09:00PM UTC by comment:2
Adding error handling to jsonp has some issues with the attached patch. These are the ones I've found so far:
Opera seems to load and execute the script synchronously so the timeout can't happen.
Firefox executes the code if it is loaded regardless of whether the timeout happens. So if a script takes 10 seconds to load and a timeout of 1 second is set. The timeout happens and reports failure to the functions. The script is removed from the document at that point, but 9 seconds later it will run. This is the only browser with this issue.
IE6/7 reports success on DNS failures and 404 document not found. I haven't found a way to figure out if it failed or not in those instances.
Safari reports success on 404 document not found (interestingly it reports failure on bad DNS unlike IE).
IMO this is an improvement over the existing code. I don't think it breaks anything that works currently, but rather fixes some of the previously failing cases. Unfortunately the bad cases aren't uniform across browsers so what works for some doesn't for others. I'm not sure which is better no error handling or inconsistent error handling.
Any ideas are welcome.
Changed May 15, 2008 02:06PM UTC by comment:4
The handler onerror works for Firefox, doesn't work on any other browsers.
I thought one could put code inside a <script> with src and it'd gets executed if the url would fail (like <object>s). But no :(