Congratulations! You found a bug! http://jsfiddle.net/8RVSt/6/ << see the fix at the top of the JS
I'll push this to the develop branch on github and it will be in the next release. On Fri, Aug 27, 2010 at 8:54 AM, Rolf -nl <[email protected]> wrote: > ah right, myForm.set('validator', new Form.Validator(myForm, { > ..but why doesnt it work like I expect it to work? > http://www.mootools.net/docs/more/Forms/Form.Validator#Element > > is it normal that it doesn't work with catching the events when using > the documented way and calling el.validate()? > > it MUST be the friday afternoon dip... 5.50pm anyway, time to leave > the office. > > On Aug 27, 4:34 pm, Gafa <[email protected]> wrote: > > with yah there about Friday. > > > > try: > > > > http://jsfiddle.net/8RVSt/4/ > > > > Gafa > > > > On Aug 27, 10:18 am, Rolf -nl <[email protected]> wrote: > > > > > If I use Form.Validator the default way I can use the events that are > > > fire like onElementFail and onFormValidate, like: > > > > >http://jsfiddle.net/8RVSt/ > > > > > (see console) > > > > > But if I make Form.Validator an instance of an element (correct way of > > > saying this?) I can check if validate() returns true or false, but > > > what happens to the events that Form.Validator fires? I can't seem to > > > "catch" them: > > > > > instance of element:http://jsfiddle.net/8RVSt/2/ > > > > > Testing it I also tried attaching the events (that Validator fiers) to > > > the element etc. but no luck either... > > > > > I'm guessing it's because it's friday and my brain can't take no more > > > JS this week that I can't wrap my head around this?!!? Cheers. >
