Hello,
In the documentation of the Calcite Input Number component; it states the following in the min & max properties:
https://developers.arcgis.com/calcite-design-system/components/input-number/#properties
Is there a reason this only works within forms? It would be nice if we could just use the min and max directly.
Kind regards,
Reint.
Hey Reint, this behavior and the property descriptions are aligned with the native HTML input with type="number" element.
The min and max properties are honored when users interact with the increment/decrement controls, but they do not prevent users from manually typing values outside the specified range both in or out of a form.
Instead, these properties are intended for form validation. When used in a form, entering a value outside the min or max constraints results in a validation failure. There's no built-in way to prevent users from entering out-of-range values without implementing custom logic, which would likely end up behaving similarly to a form validation experience.
Alright, thanks for the reply!
@DitwanDPrice wrote:this behavior and the property descriptions are aligned with the native HTML input with type="number" element.
this behavior and the property descriptions are aligned with the native HTML input with type="number" element.
That is good to know.
Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.