I am facing an issue where I encounter a problem displaying a sequence of dialogue or AJAX results that depend on each other. For instance, when a user clicks to send a message, it triggers an ajax call, which opens a dialogue box. The user fills out the form and submits it via AJAX, causing the dialogue to close. Then, another AJAX response either opens another dialogue or redirects the user. This process works smoothly in all browsers except for Safari and Chrome. Interestingly, it used to work fine previously in all browsers, but now it seems to be failing. The error function is triggered, and the browser eventually opens the URL that was used for the second AJAX request.
My implementation involves using jquery, PHP, and JavaScript. Initially, I had it set up to run from an eval(json) command. However, I have since rewritten the code to return raw JavaScript.
In any case, the error occurs in the 'error' handler of the AJAX query. The error messages returned are not very informative. I am aware that Chrome has a caching process, but I'm unsure if this affects the situation or if it exists in Safari. Nevertheless, it appears that the second AJAX call fails in Safari and Chrome before the returned JavaScript is executed. I remember it working flawlessly in all browsers before, but I'm no longer confident about that. I've already spent almost half a day trying to figure it out, so I would greatly appreciate some assistance. :D
The JavaScript function responsible for making the AJAX call is as follows:
function page(url){
$.ajax({
type: "POST",
url: url,
success : ajaxReturn,
cache: false,
dataType: 'script',
error: function(result, status, err) {
alert('HTTP ' + result.status + ' Error Encountered: ' + result.statusText);
alert(result.responseText);
alert('status: '+status+' error: '+err);
return;
}
});
}
function ajaxReturn(ret){
eval(ret);
$.unblockUI();
}
This is the same code used for both AJAX calls. In some cases, such as when an error is found in the form, the returned code is almost exactly the same. I have a well-established system for handling all dialogues, AJAX requests, and associated processes, which has been working perfectly until now.
The messages that are returned by the error handler are:
HTTP 0 Errpr Encountered: error
Followed by:
<null>
And then:
status:error error:
These messages are displayed using the alert statement. The element indicates an empty dialogue box. Therefore, despite running the same ajax functions and returning the same code, Chrome and Safari are encountering issues with the second call. Regardless of what is returned, they fail at the error handler, leaving me completely puzzled about the cause.