All Versions
25
Latest Version
Avg Release Cycle
5 days
Latest Release
1747 days ago

Changelog History
Page 1

  • v0.11.9 Changes

    January 06, 2017
    • πŸ›  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 Changes

    December 08, 2016
    • ⚑️ 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 Changes

    December 05, 2016
    • πŸ”Œ 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 Changes

    December 05, 2016
    • 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 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.
  • v0.11.2 Changes

    December 05, 2016
    • βž• Added input[type="reset"] to the ignored input filter
  • 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
  • v0.11.0 Changes

    December 05, 2016
    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)