Hi again ,
Many thanks Howard, i will continue working on this way, starting with
the analize of the Tapestry JavaScript build-in functions for
indentifying the
ones that needs to be overwritten.
Greetings4All
Passi
Howard Lewis Ship escribió:
This can be done by monkey patching the
Finally i´ve found a solution.
I have overwritten only the definition of the following object :
Tapestry.FieldEventManager = Class.create({
..
.
});
By removing all the content from removeDecorations and
showValidationMessage functions i have
exactly the validation´s behaviour i
- Original Message -
From: Howard Lewis Ship [EMAIL PROTECTED]
To: Tapestry users users@tapestry.apache.org
Sent: Saturday, November 01, 2008 6:47 PM
Subject: Re: [Tapestry 5.0.15] - Hidding client-side validation
This can be done by monkey patching the Tapestry JavaScript. You
can have
]
To: Tapestry users users@tapestry.apache.org
Sent: Saturday, November 01, 2008 6:47 PM
Subject: Re: [Tapestry 5.0.15] - Hidding client-side validation
This can be done by monkey patching the Tapestry JavaScript. You
can have a JS library that overwrites the definitions of some of the
built
This can be done by monkey patching the Tapestry JavaScript. You
can have a JS library that overwrites the definitions of some of the
built-in Tapestry functions related to validation. In this way, you
can prevent the pop up bubbles, or change how the validation messages
are presented to the
have a look in the Form component description (parameter
clientSideValidation)
http://tapestry.apache.org/tapestry5/tapestry-core/ref/org/apache/tapestry5/corelib/components/Form.html
2008/10/30 Antonio Fernández - STAR Málaga [EMAIL PROTECTED]
Hi All Good Morning :-)
Is there a way for
Hi again !
Many thanks for you fast asnwer , i tryed your option , but this is not
the behaviour i want.
Now the submit action happens when one or more TextFields are empty,
and with clientValidation=true the submit is not completed.
I want the behaviour of clientValidation=true, but
