You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Scenario : When a value in passed in, but is out of boundary (greater than max or less than min value), the value is set to the min or max boundry. This can cause data integrity issues if value is set on page load or comes in from an outside calculation, rather than being set by the user.
What did you expect to happen? What happened instead? What would you like to
see changed?
I would expect that if a value is passed to the component that is outside of the min or max value, the exact value passed is displayed, but a field validation error is also shown. This would be consistent with what currently happens if I try to manually type in a value into the component that is outside of the boundary.
What browser are you working in?
Chrome
What version of the Carbon Design System are you using?
What package(s) are you using?
carbon-components-react
Detailed description
Scenario : When a value in passed in, but is out of boundary (greater than max or less than min value), the value is set to the min or max boundry. This can cause data integrity issues if value is set on page load or comes in from an outside calculation, rather than being set by the user.
Number Input
https://react.carbondesignsystem.com/?path=/story/components-numberinput--default
I would expect that if a value is passed to the component that is outside of the min or max value, the exact value passed is displayed, but a field validation error is also shown. This would be consistent with what currently happens if I try to manually type in a value into the component that is outside of the boundary.
Chrome
Current
Steps to reproduce the issue
Result: Value is changed to 100. No error is shown.
carbon/packages/react/src/components/NumberInput/NumberInput.js
Line 42 in fb5d24e
The text was updated successfully, but these errors were encountered: