Thanks, I filed TRINIDAD-695 <http://issues.apache.org/jira/browse/TRINIDAD-695> for that issue.
Strange, though, _submitOnEnter calls submitForm with doValidate set to 0. It looks more like walkaround for some problem rather that oversight. But I'm not someone to make such a conclusions. Best regards. Danny Robinson wrote: > Vadim, > > This is definately an oversight. We'll need to add some calls to the > c/s validation into this method. Looking at the javascript I don't > think this even happens for the older ALERT based validation, let > alone the newer INLINE version. > > Can you raise an JIRA bug and we'll get this fixed asap. > > Thanks, > > Danny > > On 9/6/07, *Vadim Dmitriev* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> > wrote: > > Hi! > It looks like client-side validation is intentionally skipped if > form is submitted via tr:form "defaultCommand". Can anyone explain > why such a decision was taken by devs or just why it's useful for > client-side to be skipped in this case? > > Thanks in advance. > P.S. At least tr:form behaves like that in 1.0.2 and 3-4 days old > 1.0.3 revision. > > > > > -- > Chordiant Software Inc. > www.chordiant.com <http://www.chordiant.com>
