Yeah. Try not to depend on the internal implementation of mooTools unless absolutely necessary. I'll admit I have had to do that in several rare discrete occasions, but I don't see why you cant use form.validate(). (Unless there is a ticketed bug I am unaware of).
On Mon, Sep 7, 2009 at 9:23 PM, Aaron Newton <[email protected]> wrote: > This is not required and not really advised. If you want to know if a form > is valid, just do > if (form.validate()) ... > > > > On Mon, Sep 7, 2009 at 5:35 AM, Itay Moav <[email protected]>wrote: > >> good idea >> >> >> On Mon, Sep 7, 2009 at 3:32 AM, Thierry bela nanga <[email protected]>wrote: >> >>> I hacked the form validator I use to store the validation state in the >>> form >>> so in my event handler I just check >>> >>> if(form.retrieve('validator:state')) { >>> >>> //the form is valid >>> } >>> >>> >>> >>> On Sun, Sep 6, 2009 at 2:04 AM, Itay Moav <[email protected]>wrote: >>> >>>> What param should I send the FormValidator so it will stop the chain of >>>> submit event handlers from firing. >>>> >>>> As I understand the FormValidator adds a SUBMIT event handler to the >>>> form, and so am I in my code after that. >>>> I need the event handlers that come in the stack after the one of the >>>> FormValidator *NOT* to fire, if the form is not valid. >>>> How? >>>> (I event tried to add event.stop() inside the onSubmit method/event >>>> handler of the FormValidator, not working) >>>> >>> >>> >>> >>> -- >>> http://tbela99.blogspot.com/ >>> >>> fax : (+33) 08 26 51 94 51 >>> >> >> >
