Ajax js issue in FF 1

[Bastien]

I hav an intersting issue with the below JS code, works in IE and Chrome but not in FF. The ajax call brings back the results which I can see with Firebug. The idea is that the function gets passed the DIV parameter and checks to see what that is:
object (usually a div);
another function (to pass the results to) or
a string which gets returned to the calling function

So the only thing that doesn't seem to be executing is the div branch where the results are innerHTML'd into the div that I pass in. Am I doing something wrong in the test for the DIV with regard to FF?

function Ajax(url, data, div, Asynch)
{
// url   string   url of the page to activate
// data  string   data to be passed to the server
// div   object   div name as object,  function name to be have the result passed to when returned,   empty string to return the response to the calling function
  var objAjax = getAjaxObject();

    if (objAjax != null){

	    objAjax.onreadystatechange = function(){ 
        if (objAjax.readyState == 4) {
		           
	       if (objAjax.status == 200) {
	           strResponse = objAjax.responseText;

	           switch (typeof(div))
                   {
                     case "object":
                       if (div.style.display == 'none'){ div.style.display = 'inline'; }
                        div.innerHTML = strResponse;
                       break;

                     case "function":
                      div(strResponse);
                      break;

                     case "string":
                      return strResponse;
                      break;
                  }//end switch
                  objAjax = null;
            
              }else{
                alert("[" + objAjax.status + "]  Error: " + objAjax.reponseText);
              }//end if(objAjax.status == 200)

          }//end if(objAjax.readyState == 4) 	     
       }//end anon function
	
	    sendRequest(objAjax, "POST", url, Asynch, data);

  }//(objAjax != null)
}//end function

Bastien

I wish my computer would do what I want it to do,
instead of what I tell it to do...

 

[BillyRayPreachersSon]

Surely the most obvious thing to do is to alert typeof(div) in the section of code that checks its type, and see what Fx shows?

Dan



Coedit Limited - Delivering standards compliant, accessible web solutions

Dan's Page [blue]@[/blue] Code Couch:

http://www.codecouch.com/dan/

Code Couch Tech Snippets & Info:

http://www.codecouch.com/

 

[Bastien]

Worked it out, FF doesn't like asynch set to true for the onreadystatechange status. I set it to false and now it works

Bastien

I wish my computer would do what I want it to do,
instead of what I tell it to do...

 

[feherke]

Hi

FF doesn't like asynch set to true for the onreadystatechange status.

Once I tested this and my conclusion was that works correctly. Personally I would continue debugging.


Feherke.

http://free.rootshell.be/~feherke/

 

[Bastien]

It stated in the FF docs that it doesn't like the sync value to be true. I found it strange myself, but it's now works.

Bastien

I wish my computer would do what I want it to do,
instead of what I tell it to do...

 

[feherke]

Hi

Interesting. Thanks. I will re-read MDC.

Feherke.

http://free.rootshell.be/~feherke/

 

[Bastien]

https://developer.mozilla.org/en/xmlhttprequest

Bastien

I wish my computer would do what I want it to do,
instead of what I tell it to do...

 

[feherke]

Hi

Thanks, I saw that.

Searching the page history you may find various notes like this :

Note: Versions of Firefox prior to version 3 always call the [tt]onreadystatechange[/tt] handler even if the request is synchronous.

Then the note disappears.

( Note : I hate collaborative content. <- And this note will never disappear. )

So I am not absolutely dumb, just my knowledge is relatively outdated.

Thank you for the information, Bastien. I learned something again.


Feherke.

http://free.rootshell.be/~feherke/