Currently those field-based validation events are missing. Would you
need an event that is called whenever a field is validated? Before
validation occurs? After it's done? Only when (in)valid?
There are quite a few potential permutations, I'd like to focus on
those being actually useful.
Jörn
If the new handlers would want to extend on (be siblings of) the
invalidHandler feature, then they should be consistent with
invalidHandler's behavior. If invalidHandler fires after validation,
then that's when the new events should fire.
On a slightly different note, a passive observer may not
Thanks for the feedback. I agree that post-validation events make more
sense. The seperation of validation and message display is partially
in place - you can already use the showErrors-option to fully override
the message display.
In the meantime, here's a workaround:
var validator =
Nice; I'll get to using that. I guess all that's missing is a way to
register an onAfterCheck type event handler. :)
On Dec 8, 1:58 pm, Jörn Zaefferer [EMAIL PROTECTED]
wrote:
Thanks for the feedback. I agree that post-validation events make more
sense. The seperation of validation and
4 matches
Mail list logo