Number input converts space value to zero

[nwhittaker]

Check existing issues

• I have checked for existing issues to avoid duplicates

Actual Behavior

The <calcite-input-number> element shows a value of 0 when its value prop is programmatically set to any number of space characters.

Expected Behavior

The element ignores space values -- treating them like any other non-numeric character.

Reproduction Sample

1. Sample 1: https://codepen.io/mac_and_cheese/pen/JjgxNyr

• Open the sample
• Select the Set value to " " button
• Observe the first component's value change

2. Sample 2 (doc site) https://developers.arcgis.com/calcite-design-system/components/input-number/#sample

Reproduction Steps

1. Visit the input-number doc sample
2. Open the Properties panel, if needed
3. Enter spaces into the value field and observe the input element's displayed value
4. Compare with entering non-numeric characters into the value field

Reproduction Version

2.13.0

Relevant Info

Consider using Number.parseFloat() and/or Number.parserInt() for doing the number conversion. Number() converts empty/blank strings to 0, but the parse functions converts them to NaN.

Regression?

No response

Priority impact

impact - p2 - want for an upcoming milestone

Impact

Impact is when using <calcite-input-number> to edit untrusted data. Since the input coerces alpha characters differently then space characters, this adds an extra layer of transformation the consumer has to do to the value before handing it off to the input. Otherwise, there's ambiguity in the submission handler as to whether the coerced value should be set back in the data as 0 or cleared out/emptied.

Calcite package

• @esri/calcite-components
• @esri/calcite-components-angular
• @esri/calcite-components-react
• @esri/calcite-design-tokens
• @esri/eslint-plugin-calcite-components

Esri team

ArcGIS Field Apps