But if I specify overrideMinMaxLimits the user can visually enter anything below it. For example in the reproducible test case the user can also enter 0. Visually the behavior has changed.

That doesn't help. The solution they propose is to allow to put invalid values and mark the value as invalid. We just want the old behavior back... Null/empty would not be seen as lower than any minvalue...

Current behavior:

• When using the minimumValue we cannot clear out the number with for example backspace

Expected behavior

• The value should be cleared because NULL or empty is not a real number

Steps to reproduce the problem

• Use AutoNumeric 4.6.x
• use property minimumValue: 1
• type in a number for example 1
• do backspace
• the value is not cleared and stays on 1

This works well with version 4.5.x .!