Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More →
autonumeric
Advanced tools
autonumeric - npm Package Versions
Changelog
4.8.3
- Fixes #718 When
emptyInputBehavioris set tonull, thengetNumber()returns0when no value has been set before - Updates the
yarn clean:logcommand to clean the logs from the newer webdriver.io version - Fixes #765
changeevent is not triggered when dragging value into a text input
Changelog
4.8.1
- Fixes #763 Copyright banner in the minimized distribution file is undefined
- Removes unused wdio script from package.json
Changelog
4.8.0
- Adds #709 Feature request: Disallow toggling the negative/positive sign with '+' and '-' keypress
- This adds a new option
negativePositiveSignBehaviorfor the managing the '-' and '+' key behavior - Setting
negativePositiveSignBehaviortotruewill allow the toggling, while setting it tofalsewill 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) - Do note that the default behavior is changed in this version, where toggling between the positive and negative value with the '-' or '+' keys is not activated by default. If you want to use the previous behavior, please set
negativePositiveSignBehavior: AutoNumeric.options.negativePositiveSignBehavior.togglein your options' configuration.
- This adds a new option
- Updates the existing end-to-end tests that relied on the toggle behavior
- Fixes the incorrect error message when setting an invalid
positiveSignCharacteroption - Attempts to fix the 'node: 18' error from Travis CI
Changelog
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:
modifyValueOnUpDownArrowandupDownStep
Changelog
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
Changelog
4.6.2
- Fixes issue #757 Converted scientific numbers returns NaN when using
formArrayNumericString() - Fixes warning messages in the IDE
Changelog
4.6.0
- Adds a new option
invalidClass, which default toan-invalid, that defines the CSS class name to use when a contenteditable-enabled element value is invalid - Adds a new option value
'invalid'for theoverrideMinMaxLimitsoption, that will allow users to enter out-of-bound numbers - Fixes #543 Allow users to enter out-of-bound numbers, outside of the
minimumValueandmaximumValuerange- This allows users to type temporary invalid numbers when the
minimumValueis superior to0, or themaximumValueis inferior to0 - While in this out-of-bound state, the element validity status is set to
invalid - Users can then target the CSS
:invalidand/or:validstate as they wish to display a visual feedback as needed - Do note that contenteditable-enabled elements cannot have a validity state set, so AutoNumeric instead sets by default the
an-invalidCSS class on such 'invalid' elements - Whenever the user type an invalid number (out of range), the new
'autoNumeric:invalidValue'event is sent. When the value is corrected, the new'autoNumeric:correctedValue'event is sent.- Beware; To reduce complexity, the
'autoNumeric:invalidValue'event as well as the'autoNumeric:minExceeded'or'autoNumeric:maxExceeded'events are now sent up to three times for a single input; on keypress, keyup and blur
- Beware; To reduce complexity, the
- This allows users to type temporary invalid numbers when the
- From now on, whenever the user sets a
minimumValuehigher than0, or amaximumValuelower than0, a warning will be displayed in the console telling him to perhaps use theoverrideMinMaxLimitsinvalidoption. For information, theoverrideMinMaxLimitsdoNotOverrideis still the default behavior. - Simplify the min and max range tests with the new private
_isWithinRangeWithOverrideOption()function - Fixes the bug where you could always clear the input even if the limit were preventing you to do so (the last valid value was then set back on blur). Now AutoNumeric correctly prevents you to clear the input if the resulting value is out-of-bound.
- Fixes #676 36 errors in index.d.ts when using with typescript
- TypeScript users should now remove the
declare module 'autonumeric';line from their script (cf. PR #677)
- TypeScript users should now remove the
- Removes node 6 from the CI tests (cf. PR #678)
- Fixes the detection of wheel events when using a touchpad/trackball (cf. PR #672)
Changelog
4.5.13
- Fixes #675 The caret position is wrongly positioned when setting the raw value to zero on numbers with a prefix currency symbol (The bug was introduced in
v4.5.9with the fix for #647)