[CLOSED-33] [3.0rc2]TextField - validation fails - even when turned off

[evant]

Yes, with disableValidation set, it will only ever fire if you explicitly call validate() with some kind of "force" parameter.

[Joe]

That may do it. I still don't see a valid reason why with all field settings turned off the system validates on setValue only. Think about it .... you have a field, it does not validate when you update the value immediate, nor when you leave the field, but when you set the value using code - it runs validation and shows the error. Why?

Could you please tell me the use case / schenario you are attempting to keep from breaking by having the system validate when you setValue in a TextField, but not when you blur or keyup?

This is very inconsistant bahavior. Sure seems "buggy" if it is not an outright bug to have a setting that turns something 1/2 off ... usage of the system should be more cut and dry then that .. how will you document that? The documentation does not clearly state that with all validation turned off .. when you set a field using setValuie it runs validation anyway.

If you have a valid use case, I would like to know what that is .. maybe I'll learn a new trick.

Thanks for your replies,

[evant]

This is why we're making the changes. As the name implies validationEvent is for hooking up events to validation. Setting this to false doesn't necessarily mean you want to disable all validation, which is the premise behind adding a new parameter to forcibly disable any automatic calling of validate.

[Joe]

If disableValidation is set to false and validationEvent to false .. then I set a value using setValue .. will it still validate and show a red box?

[evant]

Yes, once again, validationEvent merely indicates a set of events to fire validation on. If this is empty, then it means don't validate on any events, but it will still be called inside setValue unless disableValidation is set to true.

[Joe]

So the system will still continue to not validate on blur and not on keyup, but when you set the value - it shows the red box for invalid. If you call that working as designed I'll simply override myself when the release hits.

Thanks for the other change and doing this volly to be sure I understand.

Regards

[evant]

Perhaps I'm not being clear. We are adding a new configuration option to disable ALL valdiation unless you explicitly call validate. validationEvent will behave as it currently does, to hook up events to validation. If the new configuration to disable validation is set, it will ignore any validationEvent.

[Joe]

Thanks for all your work in this area

It will make a huge difference in my ability to make the 3.x jump

cheers

[sumit.madan]

Perhaps I'm not being clear. We are adding a new configuration option to disable ALL valdiation unless you explicitly call validate. validationEvent will behave as it currently does, to hook up events to validation. If the new configuration to disable validation is set, it will ignore any validationEvent.

What is this new configuration option called? Could not find it in the API documentation.

I want to call validate my form manually and disable any automatic validation. validationEvent: false in field still triggers validation.