Using RadNumericTextBox in a mobile website doesn't pop up numeric keyboard in iPad. We're developing a website where the user has to enter a lot of numeric information and it has to choose the numeric pad each time it enters a new numeric field. I know that using RadTextBox and Inputtype solves this problem, but I mainly use RadNumericTextBox because it allows to specified validation like min and max values to each field. Our sales team solution is featured to be use in mobile devices thanks to the MetroTouch theme but this behaviour with numeric fields has got many negative feedbacks of our mobile users. Thanks in advanced Roberto
When it is not possible to load scripts/styles from CDN, the scripts and styles should be loaded from embedded resources. Please monitor this item as it was the original and has more votes: https://feedback.telerik.com/Project/108/Feedback/Details/119156-add-cdn-fallback-to-local-support-added-to-radscriptmanager-radstylesheetmanager
Native browser behavior is vendor specific and the above issue cannot be replicated with the latest version. Default browser in latest Android versions is Chrome and we recommend using it instead of the older native browser
Currently the datasource columns which have space in their name cannot be passed to a databound RadHtmlChart. Add the ability to handle the spaces in the names of these columns.
(limitation on Windows Phone - onkeypress event is not fired and the essential part of the RadMaskedTextBox code cannot be executed at the right time )
When the control is modal it should create a second iframe behind the modal background like it creates one behind the popup itself. This will allow the modal background to stay above heavy-weight objects in IE as well.
When a RadEditor or SPRadEditor in a custom WebPart for SharePoint 2013 is placed in an UpdatePanel or RadAjaxPanel it is not ajaxified and loses its content after a post back.
RadNumericTextBox with SelectionOnFocus="SelectAll" doesn't work in Chrome. Expected behavior: when textbox focuses, the text in the input should all be selected. Actual behavior: the cursor jumps to the end of the text in the input
Due to a bug in the WebKit-based browsers this issue could not be fixed since it will introduce another bugs in those browsers.