At the moment, you can use a "regular" input where you can add such attributes, and style it like ours: https://docs.telerik.com/blazor-ui/themes/form-elements#inputs.
In the meantime you can also try our numeric textbox that limits the input too (even if the user writes letters, there is an indication they are not allowed): https://demos.telerik.com/blazor-ui/numerictextbox/validation
Components (such as ours or any component you make in your app) will throw such exceptions when a parameter is used that is not implemented. There are two solutions to this:
- implementing the parameter in question
- implementing attribute splatting
You can Follow the implementation of additional attributes or attribute splatting for the Telerik textbox in these pages (at this point I don't know if attribute splatting will be implemented, or explicit parameters):
I also logged here an enhancement idea that the NumericTextBox we have should render type=number to guide mobile devices for the proper keyboard type, so you can Follow it too: https://feedback.telerik.com/blazor/1453380-numerictextbox-should-render-inputmode-decimal-out-of-the-box.
I must also note that a keyboard for a mobile device must be accompanied by proper validation on the server, because a user can always tamper with the input, and desktop users with physical keyboards do not benefit from customized virtual layouts. So, you may want to add a data annotation validation anyway, or use our numeric textbox that does not accept anything but numbers.
UI for Blazor