On 5/10/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
> > can you remove behaviors that validator has added? when your remove a > validator how will you know which behaviors were linked? see my previous mail (i aksed the same thing to eelco) just don't add the behavior to the behaviors just in render also walk over the validators and get the behavior if it has one. then if you remove the validator everything is gone.
but where do you keep the reference? if you create a new one on every request then these behaviors cant have state! but i see other problems comming because if validators also add stuff to the
tag like onchange or onblur. Then what happens to the other behaviors (maybe ajax) that also wants to do something?
this is a problem even now. basically we need to be careful and merge attributes instead of simply setting them (overwriting whatever was there before) -igor we are getting duplicate additions this way much much sooner.
and the worse thing is, the developer itself doesn't really know that. It doesn't do the bind itself to "onchange" for the validator that is just under water happening. Or can we use the special wicket bind event for everything? But that i guess order is again also importand. Because i think validators should happen first before other things like ajax (formsubmit behavior...) johan
