The temporal solution is to change the type attribute of the RadNumericTextBox input to "tel". This can be done in the OnLoad client event of the control:


<script>
    function OnLoad(sender, args) {
            sender.get_element().setAttribute("type", "tel");
    }
</script>
<telerik:RadNumericTextBox  RenderMode="Lightweight" runat="server" ID="RadNumericTextBox1" Width="190px" Value="1" EmptyMessage="Enter units count" MinValue="0"  ShowSpinButtons="true" NumberFormat-DecimalDigits="0">
    <ClientEvents OnLoad="OnLoad" />
</telerik:RadNumericTextBox><br />

When the "d" custom format specifier is used to format the Date or DisplayDate of RadDateInput, results are incorrect. Instead of showing only the day of the month, it shows dd/MM/yyyy. This issue affects all Picker controls that are using RadDateInput.

As a workaround, one option would be to define the DateFormat and DisplayDateFormat client-side

        <script type="text/javascript">
            function pageLoad(app, args) {
                var datetimepicker = $find("<%= RadDatePicker1.ClientID %>");
                var date = datetimepicker.get_selectedDate();
                datetimepicker.get_dateInput().set_dateFormat("d");
                datetimepicker.get_dateInput().set_displayDateFormat("d");
                datetimepicker.set_selectedDate(date);
            }
        </script>

another option could be to put a space or a two signle-quotes before or after the format specifier letter in the markup:

e.g.
DateFormat=" d"
DateFormat="d "
DateFormat="''d"
DateFormat="d''"

<telerik:RadDateInput ID="RadDateInput1" runat="server" DateFormat="d " DisplayDateFormat="d " SelectedDate="4/17/2018"></telerik:RadDateInput>

The RadMaskedTextBox DisplayMask does not work properly in case "*" is used in it.

 DateInputSetting in InputManager does not behave as expected.

Use  the code and steps below:

<telerik:RadInputManager ID="RadInputManager1" runat="server">
    <telerik:DateInputSetting BehaviorID="BehaviourFormatHeure" DateFormat="HH:mm:ss" Validation-ValidationGroup="GroupValidation">
        <TargetControls>
            <telerik:TargetInput ControlID="txtHeureDebut"></telerik:TargetInput>
            <telerik:TargetInput ControlID="txtHeureFin"></telerik:TargetInput>
        </TargetControls>
    </telerik:DateInputSetting>
</telerik:RadInputManager>


When  type 5 and quit the input field, it works : 05:00:00 appears
When  type 512 and quit the input field, it works too : 05:12:00 appears
When  type 05:12:27 and quit the input field, it works again : value is unchanged
But when type 051227 and quit the input field, an error is indicated

RadTimePicker :
           Currently the time picker with time interval 5 minutes shows a large list. Instead of large list display Hours 1 to 12 with AM and PM and Minutes 05 to 55 like the image enclosed. 

A property to handle that would be very convenient. This way developers could be able to restrict the number of rows that the user can type. Something like MaxRowNumber.

Additionally, a property MaxColumnNumber would be also useful to restrict the length of each row. 

Currently if the MinValue or MaxValue properties are changed on the client, on the server the numeric value is auto-corrected according to the their old value.

Disabling the ViewState can help. Here is a basic example that can be used:

		<telerik:RadNumericTextBox runat="server" ID="rtb1" EnableViewState="false"></telerik:RadNumericTextBox>
		<asp:Button ID="Button1" Text="1 change max value and value with JS" OnClientClick="changeValues(); return false;" runat="server" />
		<asp:Button ID="Button2" Text="2 postback" OnClick="Button2_Click" runat="server" />
		<script>
			function changeValues() {
				var rtb = $find("<%=rtb1.ClientID%>");
				rtb.set_maxValue(100);
				rtb.set_value(100);
			}
		</script>

	protected void Page_Load(object sender, EventArgs e)
	{
		if (!Page.IsPostBack)
		{
			rtb1.MaxValue = 20;
			rtb1.Value = 1;
		}
	}
	protected void Button2_Click(object sender, EventArgs e)
	{
		Response.Write(string.Format("currValue: {0}<br/> maxValue: {1}", rtb1.Value, rtb1.MaxValue));
	}

Title says it all really. The current functionality is clunky and doesn't persist and it should.