Replace that with form.submit(), which triggers the native submit event instead and not the validation.
Adding validation rules to controls in a form template ensures that the data collected is accurate and consistent.
If not, please let me know about any ideas you may have for improvements! Throughout the documentation, two terms are used very often, so it's important that you know their meaning in the context of the validation plugin: The validate method returns a Validator object that has a few public methods that you can use to trigger validation programmatically or change the contents of the form.
By basing a rule on a set of signable data, you can add an error message to a submit button if a user has not signed the form, thus helping to ensure that the form is signed before submitting.Of course that isn't the only way to specify rules.You also don't have to rely on those default messages, but they come in handy when starting to setup validation for a form.That behaviour can be irritating when clicking through demos of the validation plugin – it is designed for an unobtrusive user experience, annoying the user as little as possible with unnecessary error messages.So when you try out other demos, try to react like one of your users would, and see if the behaviour is better then.If you've decided to use the validation plugin in your application and want to get to know it better, it is recommended that you read the guidelines.