Re: [KCFusion] a design question (off topic)

[Adaryl Wakefield]

Thanks Daryl. I usually submit the form in the function with the js submit() method. If having it return true/false is better I will go that route in the future. A. ----- Original Message ----- From: Daryl Banttari To: [EMAIL PROTECTED] Sent: Saturday, December 07, 2002 2:07 PM Subject: Re: [KCFusion] a design question (off topic) Adaryl,   The onClick handler for submit buttons requires that you return a "true" or "false" value from the handler, which determines whether or not the form submission actually happens.  If you wanted the form to actually submit after the "goEmail()" function completes, you'd do this:     Conversely, if you did not want the form to submit, you'd return false.  If you want goEmail() to decide whether the form submits, have the function return a true or false value, and code the submit button's onClick handler this way:     n.b. The use of "javascript:" is only requred in HREF attributes of links; and onClick handlers work similarly for links (they should also return "true" or "false" to indicate whether the link should actually followed.)   If you don't return a true/false for an onClick handler in these cases, the behavior is undefined/unpredictable.   HTH   --Daryl   ----- Original Message ----- From: Adaryl Wakefield To: [EMAIL PROTECTED] Sent: Wednesday, December 04, 2002 4:12 PM Subject: [KCFusion] a design question (off topic) I've hit an odd issue. I have a simple submit button that calls a js function when clicked. The problem is it does not work in Netscape6 (go figure). The buttons don't even respond to mouse clicks or anything its all very odd. This is not normally part of my job (graphics, yik)  and I know some of you do this full time. The tag looks like this: <input type="Submit" name="email" value="Go" > Anybody see anything glaringly wrong with it? A.