On Fri, 03 Aug 2012 04:57:02 -0300, mem
wrote:
value has to parsed, probably ending up in the same situation as i'm now
with the production mode. So i guess i'm stuck with adding the css
classes just manually to the fields.
Instead of implementing a ValidationDecorator, you could implemen
e answer.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Example-of-overriding-the-default-ValidationDecorator-tp2419072p5715029.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To u
bjects when not using production
> mode.
> I couldn't figure out why that is, does anyone have an explanation for this
> behavior or any clues where/what to search for?
>
> Thanks in advance.
>
> Matt
>
>
>
> --
> View this message in context:
> http:/
iew this message in context:
http://tapestry.1045711.n5.nabble.com/Example-of-overriding-the-default-ValidationDecorator-tp2419072p5714940.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe,
> Unfortunately it seems that it does not help against these error-
> bubbles.
To override the client side you'll need to read tapestry.js and follow some of
what it does. Personally I feel that the error bubbles should not be part of
the T5 core, but an optional example validation module.
I cr
Thanks Thiago, that helped me a lot.
Unfortunately it seems that it does not help against these error-bubbles.
Piero
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h.
Hi!
I'd never tried to override the default ValidationDecorator.
It adds the "invalid-field" CSS class to fields that have validation
errors and to their labels. For each required field, it adds an asterisk
after its label. In addition, it writes the error message after the field
inside a
