All Versions
25
Latest Version
Avg Release Cycle
5 days
Latest Release
2932 days ago
Changelog History
Page 1
Changelog History
Page 1
-
v0.11.9 Changes
January 06, 2017 -
v0.11.8 Changes
December 08, 2016 -
v0.11.7 Changes
December 05, 2016 -
v0.11.6 Changes
December 05, 2016 -
v0.11.5 Changes
December 05, 2016- π Fixed an event binding order issue when the form is reset. (#375)
-
v0.11.4
July 16, 2016 -
v0.11.3 Changes
December 05, 2016- π Fixed
.has-success
not being cleared if a field.has-feedback
and has it's value cleared. Shoutout to @net for bringing the bugs fixed in 0.11.1 - 0.11.3 to my attention.
- π Fixed
-
v0.11.2 Changes
December 05, 2016- β Added
input[type="reset"]
to the ignored input filter
- β Added
-
v0.11.1 Changes
December 05, 2016- β Added a
reset
event listener on the form to reinitialize the plugin - π Fixed a missed bit of cleanup in
.validator('destroy')
where it wasn't removing the.has-success
class
- β Added a
-
v0.11.0 Changes
December 05, 2016BREAKING CHANGES: - Custom validators are now expected to return an error string if the field is invalid.
- π The errors option has been removed. Override
$.fn.validator.Constructor.DEFAULTS.errors
if you want to change the defaultmatch
andminlength
errors. - The validator no longer skips disabled/invisible fields. If you want this behavior back, add
$.fn.validator.Constructor.INPUT_SELECTOR += ':enabled:visible'
to your code. (#115) (#134) (#317)
Enhancements: - β Added support for distinct custom errors for the standard HTML5 attribute validators. No more being stuck with
data-native-error=""
for all of them. (#222) (#241) (#285) - β Added a
.validator('update')
method to refresh the set of fields that will be validated (#306) - β Added support of
data-validate="true|false"
on inputs to force validation of that field - Immediately validating fields that already have a value upon validator initialization (#350)
π ###### Bugfixes:
- π Fixed a bug in Safari where
element.checkValidity()
was returning stale values (#293) - π Fixed a bug where spaces at the end of inputs were being trimmed off before being run through validators (#338)
- Custom validators no longer leak to other instances of Validator. (#176)
- π» Scrolling with
focus: true
option is now triggered on$('html, body')
instead of$(document.body)
for better cross-browser support (#282) - β Removed (value == previousValue => skip) optimization. It was breaking the match validator and wasn't improving perf that much. (#316) (#340)
- β Added
$.fn.validator.Constructor.VERSION
property for parity with core Bootstrap plugins
π ###### Docs Changes:
- π Docs: Added an Overview section which calls out that whatever conventions apply to Bootstrap's core plugins also apply here
- π Docs: Added a callout blurb about the standard attribute validators
- π Docs: Added a "Validated fields" section to document the Validator.INPUT_SELECTOR field
- π Docs: Removed
$()
from method headers, which was confusing some people (#202)