Testing within the emulator (Oreo 8.1 API27 Google APIs) the correct keyboard is displayed so that I can enter values using the decimal precision.
However, for two physical devices I use for testing, I do not have the keyboard to provide for negative or decimal precision, only numbers.
Those devices being:
Samsung Galaxy Tab S2 9.7
Samsung Galaxy Tab A 8.0
Using other Android apps that do not leverage the Syncfusion control on these devices displays the correct keyboard. To further complicate, the keyboard selection on two iPads also exhibit the keyboard selection issue with this control.
I installed the sample app from the Google Play store and the NumericTextBox does not display the decimal/negative sign keyboard - but the NumericUpDown demonstration does.
RMRobert MimsDecember 7, 2018 01:03 PM
Switching to the NumericUpDown control, same bindings and precision and the correct keyboard shows.
Suggests something with the Numeric Textbox control.
PAPaul Anderson S Syncfusion Team December 11, 2018 08:02 AM
Greetings from Syncfusion.
We have analyzed the reported issue in source level. We have used key listener in SfNumericTextBox. So only the key board issue occurs in Tablets. To overcome this issue we have changed the keyboard type in the rendered of the control using the below snippet.
That is almost exactly how I am working around the issue for this and the iOS issues you are looking at in incident 222710.
RMRobert MimsDecember 11, 2018 11:31 AM
For reference, conceptually, look at the configuration and add behaviors with the correct keyboard, no matter the Idiom.
One observation, however, is that these only seem to work for Android. For iOS, the NumbersAndPunctuation keyboard always appears, despite validation of assignment in the renderer and UWP does not appear to honor the InputScope designation (comes in null) for the control - even with the known limitations with keyboard customization.