javascript function does not work in mozilla firefox

[sanjeeb]

I have been using the following javscript code to validate form it work smoothly in IE but not in mozilla firefox
please anybody tell me the solution of this problem

the code is

function MM_validateForm() { //v4.0

var i,p,q,nm,test,num,min,max,errors='',args=MM_validateForm.arguments;

for (i=0; i<(args.length-2); i+=3) { test=args[i+2]; val=MM_findObj(args[i]);
if(val==null){ val=document.forms["newsletter"].EMail; alert("sanjeev"); }
if (val) { nm=val.name; if ((val=val.value)!="") {
if (test.indexOf('isEmail')!=-1) { p=val.indexOf('@');
if (p<1 ¦¦ p==(val.length-1)) errors+='Email Box must contain an e-mail address.\n';
else {p=val.indexOf('.');
if (p<1 ¦¦ p==(val.length-1)) errors+='Email Box must contain an e-mail address.\n';}
} else if (test!='R') { num = parseFloat(val);
if (isNaN(val)) errors+=nm+' Box must contain a number.\n';
if (test.indexOf('inRange')!= -1) { p=test.indexOf(':');
min=test.substring(8,p); max=test.substring(p+1);
if (num<min ¦¦ max<num) errors+=nm+' Box must contain a number between '+min+' and

'+max+'.\n';
} } } else if (test.charAt(0) == 'R') {if (test.indexOf('isEmail')!=-1)errors += 'Email can not

be blank.\n';
else errors +=nm+' can not be blank.\n'; }}
} if (errors) alert('The following error(s) occurred:\n'+errors);
document.MM_returnValue = (errors == '');
}

function MM_findObj(n, d) { //v4.01
var p,i,x; if(!d) d=document; if((p=n.indexOf("?"))>0&&parent.frames.length) {
d=parent.frames[n.substring(p+1)].document; n=n.substring(0,p); }
if(!(x=d[n])&&d.all) x=d.all[n]; for (i=0;!x&&i<d.forms.length;i++) x=d.forms[i][n];

for(i=0;!x&&d.layers&&i<d.layers.length;i++) x=MM_findObj(n,d.layers[i].document);
if(!x && d.getElementById) x=d.getElementById(n); return x;

-> in function MM_findObj(n, d) X return object in case of IE while in case of mozilla X return null

I could'nt understand why X retun null in mozilla

[txbakers]

Boy do I hate that Dreamweaver validation routine. So much gobbledygook in there.

My advice, for what it's worth, is to throw that out and write your own, one you can understand and debug as needed.

That's a mess.

Most likely the issue is the way FF handles the DOM.