RadMaskedTextBox does not work properly on Android devices

Progress® Telerik® UI for ASP.NET AJAX Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Won't Fix

Last Updated: 03 Dec 2019 10:03 by ADMIN

ADMIN

Marin

Created on: 23 Oct 2013 15:11

Category: UI for ASP.NET AJAX

Type: Bug Report

RadMaskedTextBox does not work properly on Android devices

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

9 comments

ADMIN

Rumen

Posted on: 03 Dec 2019 10:03

Hi Mohit,

Can you explain in more detail the problem you experience as well as specify the browser name/version and Android version?

I tested both demos:

on Samsung Galaxy S10+ under the latest Google Chrome and I was able to type without problems in the masked textboxes.

Regards,
Rumen
Progress Telerik

Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.

MOHIT

Posted on: 27 Nov 2019 07:29

Issue still exist with the latest telerik dll (2019)

silvio

Posted on: 05 Sep 2018 23:05

well....

Yan

Posted on: 02 Jun 2015 17:51

Wooh! I'm not alone posting here!!

I was told in another thread that they will check this issue soon!!

http://www.telerik.com/forums/radmaskedtextbox-not-working-with-mobile-browsers#sVQW0713HkSvNmL_0T3LPw

Bill

Posted on: 31 May 2015 05:39

Suggested work arounds should be provided at least...

Yan

Posted on: 21 May 2015 13:49

An ETA would be appreciated...

Yan

Posted on: 14 May 2015 14:36

Hi,  this bug is approved for nearly 2 years,  do you think it's going to be fix soon?

Yan

Posted on: 26 Feb 2015 16:10

Hello,  could someone answer about when you think this could be fixed?  We are experiencing this bug and no android user can use our site at the moment....

Yan

Posted on: 23 Feb 2015 17:59

Hi,

We are currently experiencing this bug.  was this issue solved?