Releases: haacked/aspnet-client-validation
Relax on the URLs
What's Changed
Full Changelog: v0.5.0...v0.5.1
Contributors
Assets 2
The hidden are not invalid
Contributors
Assets 2
More Unobtrusive Improvements v0.4.0
This release consists entirely of 3rd party contributions. Thanks @skttl!
What's Changed
- Adds method for focusing first invalid field upon validation. by @skttl in #6
- Adds
isValid(form)method for checking whether a form is valid by @skttl in #8 - Fixes bug when using
v.validateForm()by @skttl in #9
New Contributors
Full Changelog: v0.3.0...v0.4.0
Contributors
Assets 2
Validation Event Choice v0.3.0
- Add support for choosing the event that triggers validation
By default, input fields are validated when the input event fires. In other words, when the input changes. Now you can control it so a field validates on blur for example: <input type="text" data-val-event="blur" ... />
Load Timing v0.2.3
- Update the
bootstrapmethod to set up client validation earlier
Prior to this change, the bootstrap method waited till the window load event fired. Now it checks to see if the document is loaded and if not, sets everything up when the document DOMContentLoaded event is fired.
Submit Propagation Nation v0.2.2
NOTES
A form may have other event handlers attached to the submit event. For example, when implementing an Ajax form. Rather than call the
submit method directly which bypasses those handlers, if the form is valid, this allows the original form submit event to propagate.
However, if the form is invalid, this stops propagation of the form event entirely, even to other registered event handlers. This is usually what you want. If not, then we can add options later.
IMPORTANT: This requires that client validation registers its event handler on forms first.