Using 1.0.0-beta0 (b2019021702)
When using input bounds on a numeric input, if the entered value is outside the configured input bounds at any time (even prior to pressing enter), the final value will not be accepted.
e.g. minimum inputBound is 5
If the user enters 50, the entry is accepted because 5 is accepted, as is 50.
However if the user enters 49, the input is rejected because for a short time, the entry was “4” which is outside the permitted bounds. If the user enters the 9 first, then moves the cursor to the left of the 9 to enter the 4, the entry is accepted as both “9” and “49” are above the minimum of 5.
Likewise if the entry currently reads 35, and the user backspaces the 5 to enter a 6, the entry is rejected as the entry was briefly 3. However if the user selects the 5 and types a 6, the entry is accepted as the entry was changed directly from 35 to 36, which are both accepted.