(And binding an event to onclick or onsubmit doesn't mean that existing
handlers have to go away, depending on how you do it, or if you save
existing handlers.)
On Thu, Sep 23, 2010 at 1:51 PM, Dale Newfield <d...@newfield.org> wrote:
> On 9/23/10 7:48 AM, Robert Taylor wrote:
>
>> I'm not sure modifying the templates will work here.
>>
>
> css_xhtml/form-validate.ftl contains:
>
> <#if parameters.onsubmit??>
> ${tag.addParameter('onsubmit', "${parameters.onsubmit}; return
> validateForm_${parameters.id}();")}
> <#else>
> ${tag.addParameter('onsubmit', "return validateForm_${parameters.id
> }();")}
> </#if>
>
> If you override that file and change one line like so:
>
> <#if parameters.onsubmit??>
> ${tag.addParameter('onsubmit', "return (validateForm_${
> parameters.id}() && ${parameters.onsubmit});")}
> <#else>
> ${tag.addParameter('onsubmit', "return validateForm_${parameters.id
> }();")}
> </#if>
>
> and make your onsubmit attribute just be javascript that generates a
> true/false value (FOO) instead of "return FOO", then I think you'll get what
> you want.
>
> -Dale
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
> For additional commands, e-mail: user-h...@struts.apache.org
>
>
