4.10.4

Fixes the handling of a wheel event with a deltaY equal to zero

4.10.2

Fixes #773 Typescript types in index.d.ts missing/wrong

You may now have a better experience using AutoNumeric with Typescript.

4.10.1

Fixes #776 On rapid event wheel emissions, deltaY of value 0 can be emitted and makes AutoNumeric throw an error

4.10.0

This release brings a potentially important change if you use AutoNumeric on very old browsers.
Since Microsoft dropped support for IE11 a few years ago, we decided to drop its support as well from AutoNumeric.
Starting in 4.10.0, IE11 is no longer supported by AutoNumeric.

4.9.0

• Closes #728 Unable to group by 2 using digital group spacing options

Changes:

• This version modifies the AutoNumeric.options.digitalGroupSpacing.two option, which is now named AutoNumeric.options.digitalGroupSpacing.twoThree
• The AutoNumeric.options.digitalGroupSpacing.two now effectively groups only by 2 (and not by 2 and 3 like before for India's numbering system)

4.8.4

• Fixes #768 unformatOnSubmit does not unformat fields located outside of form DOM subtree
• Updates the function that search for form children to also include the contenteditable elements

Changes:

• All form functions relying on the _getFormAutoNumericChildren() function will now correctly include all inputs and contenteditable elements

4.8.3

• Fixes #718 When emptyInputBehavior is set to null, then getNumber() returns 0 when no value has been set before
• Updates the yarn clean:log command to clean the logs from the newer webdriver.io version
• Fixes #765 change event is not triggered when dragging value into a text input
  Now, dropping a valid value into an AutoNumeric element, will trigger a change event if said value is different from the one already in the element
• Fixes PR #731 by avoiding "Forced reflow" when calling the _historyTableAdd() function

Changes:

• When emptyInputBehavior is set to null and no default or intial value is passed during initialization, then getNumber() will now return null instead of 0 like before.

4.8.1

• Adds #709 Feature request: Disallow toggling the negative/positive sign with '+' and '-' keypress
  • This adds a new option negativePositiveSignBehavior for the managing the '-' and '+' key behavior
  • Setting negativePositiveSignBehavior to true will allow the toggling, while setting it to false will disable it; this means that when hitting the '-' key, the value will always be set to its negative value, and hitting the '+' key will always set the element to its positive value (given the minimum and maximum value allows this)
• Updates the existing end-to-end tests that relied on the toggle behavior
• Fixes the incorrect error message when setting an invalid positiveSignCharacter option
• Attempts to fix the 'node: 18' error from Travis CI
• Fixes #763 Copyright banner in the minimized distribution file is undefined
• Removes unused wdio script from package.json

Changes:

• By default the - and + key will not toggle the negative/positive state of an AutoNumeric element anymore.
• The default behavior has changed in this version, where toggling between the positive and negative value with the '-' or '+' keys is not activated, instead - will try to set the value negative, and + will try to make it positive (this can fail if the resulting value is out of bounds).
• If you want to use the previous behavior, please set negativePositiveSignBehavior: AutoNumeric.options.negativePositiveSignBehavior.toggle in your options' configuration.

4.7.0

• Fixes #719 Feature request: Up and down arrow keys behavior matching standard number input
• Adds 2 new options to control how the up and down arrow keys behave: modifyValueOnUpDownArrow and upDownStep

Changes:

• By default the up and down arrows will now increment and decrement the element value like any 'numeric' input does. You can get back the previous behavior by setting modifyValueOnUpDownArrow: false in your options.

4.6.3

• Fixes #721 AutoNumeric.set() breaks internal state when string-value has leading or trailing whitespace
• Fixes all the remaining end-to-end tests with the latest Webdriver.io version
• Removes the remnants of PhantomJS hacks (#384)
• Updates the Travis CI configuration
• Fixes the caret positioning in some specific cases
• Fixes the lint issues in the wdio config file
• Fixes the webpack production config to correctly generate gzipped dist files