Hi all,
as a quick follow up on the client side validation issue in T 4.1.1 I posted
earlier, I've just upgraded to T 4.1.5, which seems to have solved the
problem.
Nils
On Mon, Jul 14, 2008 at 3:17 PM, Nils Preusker <[EMAIL PROTECTED]>
wrote:
> Hi all, I ran into a strange problem with client
Hi all, I ran into a strange problem with client side validation in tapestry
4.1.1. When I use the number translator and enable client side validation in
a form with an integer value and I enter a value larger than 999, I get the
error message "SomeInt must be a numeric value.". After some debuggin
