[Number input web component max/min attribute issue]: step attribute does not work as expected when max set to 2147483647 and min set to -2147483647

[AleemaMalik]

Description

The following number-input works as expected. When the +/- icons are clicked, the number increases by step amount

  <cds-number-input
    value="0"
    min="0"
    max="100"
    step="2"
    label="Label text"
    helper-text="Optional helper text">
  </cds-number-input>

However, when the max and min are set to the following, we see some weird behavior

  <cds-number-input
    value="0"
    min="-2147483647"
    max="2147483647"
    step="2"
    label="Label text"
    helper-text="Optional helper text">
  </cds-number-input>

Actual Behavior
Anytime the +/- icon is clicked the number increments by 1, then it beings to increment by step amount
0 -> 1 -> 3 -> 5 -> 7 ..

Expected behavior
Anytime the +/- icon is clicked the number should increment by the step amount
0 -> 2 -> 4 -> 6 -> 8 ..

Component(s) impacted

number-input

  <cds-number-input
    value="0"
    min="-2147483647"
    max="2147483647"
    step="2"
    label="Label text"
    helper-text="Optional helper text">
  </cds-number-input>

Browser

No response

Carbon for IBM.com version

"@carbon/web-components": "^2.8.0",

Severity

Severity 2 = Aspects of design is broken, and impedes users in a significant way, but there is a way to complete their tasks. Affects major functionality, has a workaround.

Application/website

Universal Automation Builder

Package

@carbon/web-components

CodeSandbox example

https://codesandbox.io/p/live/53b9014a-822a-4fad-9138-3bc4cee65bf1

Steps to reproduce the issue (if applicable)

Create a number-input component with min = -2147483647 and max = 2147483647 . Set a step value to any value greater than 1.

  <cds-number-input
    value="0"
    min="-2147483647"
    max="2147483647"
    step="2"
    label="Label text"
    helper-text="Optional helper text">
  </cds-number-input>

Release date (if applicable)

No response

Code of Conduct

• I agree to follow this project's Code of Conduct
• I checked the current issues for duplicate issues