v0.11.9

@1000hz 1000hz released this Jan 6, 2017 · 1 commit to master since this release

  • Fixing another issue with <select multiple/> elements. (#463)
  • No longer skipping a custom validator if its attribute has a falsy value. (#475)
  • Fixing stale values being read for data-attributes.

v0.11.8

@1000hz 1000hz released this Dec 8, 2016 · 6 commits to master since this release

  • Properly updating the submit button state when you run .validator(‘update’). (#461)
  • Clearing errors on fields with data-validate="false" upon calling .validator('update'). (#387)

v0.11.7

@1000hz 1000hz released this Dec 5, 2016 · 9 commits to master since this release

  • Skip auto-validation of fields with errors that were set before plugin init. (#401)
  • Fixing non-multiple select validation, which accidentally broke in the last release. (#453)

v0.11.6

@1000hz 1000hz released this Dec 5, 2016 · 12 commits to master since this release

  • Scope focus option's error scrolling to only inputs within the validator's form element. (#385)
  • Fixing <select multiple required /> being marked as invalid by default with jQuery 3.x (#393)
  • Fixing a memory leak of this.$inputs on .validator('destroy')

v0.11.5

@1000hz 1000hz released this Dec 5, 2016 · 27 commits to master since this release

  • Fixed an event binding order issue when the form is reset. (#375)

v0.11.3

@1000hz 1000hz released this Dec 5, 2016 · 35 commits to master since this release

  • 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.

v0.11.2

@1000hz 1000hz released this Dec 5, 2016 · 37 commits to master since this release

  • Added input[type="reset"] to the ignored input filter

v0.11.1

@1000hz 1000hz released this Dec 5, 2016 · 39 commits to master since this release

  • 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

v0.11.0

@1000hz 1000hz released this Dec 5, 2016 · 44 commits to master since this release

BREAKING 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 default match and minlength 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)