NumberInputV2

Use NumberInputV2 to let users enter integers and floating-point numbers.

OverviewPropertiesUsageMigrationChangelog3.14.0

Changes to NumberInputV2. The full components changelog also lists package-wide and cross-cutting entries.

3.10.0

Updates

Forms

• Added onFocus and onBlur props to TextInput, TextArea, NumberInputV2, PasswordInput, SearchInput, Checkbox, Radio, RadioGroup, Switch, ToggleButtonGroup. TextInput, NumberInputV2, PasswordInput, SearchInput, RadioGroup, and ToggleButtonGroup only fire the blur when focus leaves the entire component, not on internal transitions (e.g. tabbing from the input to a suffix button).

3.9.0

Updates

• Range/step validation errors (min/max/step) now block form submission and are no longer cleared when the required prop changes. (APPDEV-18575)

3.4.0

Updates

General

• Behavior tracking attributes are now supported in all button components, including Button, IntentButton, NotifyButton, and RunQueryButton. (APPDEV-16876)
• The text and icon color tokens for the success on accent button are now correct. (APPDEV-17388)
• Behavior tracking attributes are now supported in all form components, including Calendar, Checkbox, DateTimePicker, DateTimeRangePicker, FieldSet, FormField, Label, NumberInput, NumberInputV2, PasswordInput, Radio, SearchInput, Select, Switch, TextArea, TextInput, and ToggleButtonGroup. (APPDEV-16882)
• Behavior tracking attributes are now supported in FilterBar, FilterField, SegmentSelector, and TimeframeSelector. FilterField.Suggestions and TimeframeSelector.Presets now also support behavior tracking attributes. (APPDEV-16881)
• Added feature flag and css overrides for design tokens for visual refresh. (APPDEV-17223)

3.1.0

Updates

• Introduce NumberInputV2. NumberInputV2 aligns with the current forms architecture and delivers more consistent input behavior across Strato form controls.

API changes to consider when migrating:

• min and max now accept number | undefined (previously number | string | undefined).
• Parsing/formatting is stricter and locale-aware, including intermediate input states and paste normalization.
• step vs stepMultiplier: - step defines the valid value interval for validation and the base increment/decrement amount (for example step={0.5} only allows values aligned to 0.5 and steps by 0.5). - stepMultiplier is a positive integer multiplied by step (or 1 if no step is set) to determine how much the value changes when using arrow keys, the scroll wheel, or the stepper buttons. - You can combine both: e.g. step={0.5} to validate allowed values and stepMultiplier={4} to increment/decrement by 2. (APPDEV-3996)