in general I appreciate now having a number input component, but currently there are still a few issues and inconsitencies:
Potentially a bug: Strange behavior when using the Number Input control in galleries.
If you click directly on one of the steps buttons, the onChanges fires, but the value is not updated. It only happens after a few consequtive click,
Or only when you first click into the number field, to give it focus and start using the buttons, it works directly.
This way it impacts user acceptance and we cannot really use it in galleries. We don't have the issue outside of galleries.
It seems that the onChange of the modern control is fired on initialization, which is inconstistent with the other controls. would be nice if this could be harmonized.
It actually creates some problems when initializing all necessary data, especially when using Number Inputs in galleries.
It should only be triggered by direct user interaction.
Minor topics:
It does not have a "Fill" property. I.e. its white thus you cannot use it in all use cases, e.g. in which you want to change the fill, while this is possible with the Text control.
Currently we are helping ourselfes by using an additional label control, which would be otherwise required. Only way to "fake" a specific fill is, to use borders, but this won't work, if the control is disabled or view only.
It would be create, if the Step buttons could also grow in height, if the height of the control is increased, for better usability.
Don't use a modern control if you experience issues. Substitute for a classic control....
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
13
Share
Report
All responses (
Answers (
