Munson, Jacob wrote: > I'm having trouble following your logic, but I'd think if you have one > function in the onBlur of an input, and the other in the onSubmit of the > form tag, it should keep them separate. What's causing them both to > fire? > They both fire in the event of someone making a change to the email address, and hitting 'return', submitting the form. If the qForms validation (triggered by the submit) finds a problem, it throws up an alert - causing the 'email' field to blur, which then triggers the Ajaxified code.
As best I can tell, I can't simply change the 'submit' button to a 'button' button and throw a 'submit()' call in the onClick for that button, as qForms seems to rely on a normal form submittal as opposed to the form being submitted via a JS call. I had a coworker testing this, and depending on what he did, it would throw him into an infinite loop of alerts, which is the main reason I'm trying to get this resolved. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:262947 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
