how very interesting. i didn't even really think about anything "launching"
the javascript. after one hit the submit button, one was taken to the action
page which contained right off the bat the custom form validation tag. if
there was a problem with one of the relevant form fields, that chunk of
javascript was simply run.
just for kicks, i amended the below code to be a little more formal:
<cfif len(trim(errormessage))>
<cfoutput>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<script language="JavaScript">
<!--
function displayError() {
alert('#errormessage#');
history.go(-1);
abort;
}
//-->
</script>
</head>
<body onLoad="displayError();"></body>
</html>
</cfoutput>
<cfabort>
</cfif>
and NN 6.1 now is having no problems with it and is doing exactly what it
should be doing. apparently, the newer browser versions are more particular
about structure or something.
in any event, judith (judy?), your reply got me thinking down a different
path, so thank you very much!
~kamie
Judith Campbell wrote:
> What event is launching your javascript. It's possiby that Netscape 6 is
> handling the onload event diffrently , if that's what you're using.
>
> At 04:35 PM 8/29/01 -0400, you wrote:
> >okay, i've run out of ideas and am hoping someone on this list can help.
> >
> >after hitting the submit button, my code calls upon -- first thing in
> >the form's action page -- an in-house custom tag that does some form
> >validation. if anything in the form is not correct, a javascript pop-up
> >lets the user know what isn't right. this tag, which we've been using
> >for years, has worked beautifully in all browsers. for some reason, NN
> >6.1 is not liking it. instead of popping up the message and kicking the
> >user back to the form, NN 6.1 duplicates everything in the javascript,
> >which means popping up the message twice and kicking the user back two
> >pages to the shopping cart (which means they have to fill out their
> >contact/payment info all over again -- not good!). why is this
> >happening??? has anyone else encountered similar behavior with NN 6.1?
> >
> >after doing the form validations, here is the code in the custom tag:
> >
> ><cfif len(trim(errormessage))>
> > <cfoutput>
> > <script language="JavaScript">
> > <!--
> > alert('#errormessage#');
> > history.go(-1);
> > abort;
> > // -->
> > </script>
> > </cfoutput>
> > <cfabort>
> ></cfif>
> >
> >any thoughts would be much appreciated. thanks!
> >
> >~kamie
--
Kamie B. Curfman
Matrix Group International, Inc.
801 N. Fairfax Street, Suite 205
Alexandria, VA 22314
Phone: (703) 838-9777 x3014
Fax: (703) 838-9799
[EMAIL PROTECTED]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
