NumericInput doesn't constain min and max on text entry

[thejjmiller]

When you have a min and/or max property specified only the up and down arrows are constrained. You can still type in much larger or smaller numbers.

[cmslewis]

@thejjmiller We've thought about this in the past. This is not technically a bug; this is consistent with how default input[type="number"]s work.

EDIT: If we wanted to enforce min/max thoroughly, we'd probably do it on blur in addition to on increment. But then there are a few choices:

1. On blur, clamp out-of-range values (to min/max).
2. On blur, clear out-of-ranges values.
3. On blur, set out-of-range values to 0.

What would you expect?

[thejjmiller]

I agree. That is how I implemented it on my own. On blur set the value to max if it is over max and if under min set to min.

I understand that is what input[type=number] does but still seems like part of having a framework like blueprint is to help fix some of those problems.

Also wanted to say that we really have loved Blueprint and love getting so many new releases.

[cmslewis]

@thejjmiller I opened a PR. Take a look! #1057

[thejjmiller]

Thank you. Works perfect now.