Hey everyone,
Recently we have upgraded Telerik controls in our application to latest version and run into a few bugs with RadMaskedTextBox that can be reproduced on latest version of MS Edge.
I provided Telerik demo web-page instead of source code.
Case 1: Cursor changes position after entered letter
- Focus on 'Phone' field
- Enter any letter
Expected result: cursor doesn't change position as it works in Chrome or Firefox.
Actual result: cursor change position and moves to right side.
Case 2: Page freezes while entering value
- Focus on 'Phone' field
- Enter '1234' repeatedly and press Home button in the end of the field and enter value again
Expected result: new value is replacing the old one
Actual result: at some point page freezes, user unable to do anything on the current page
Last case can be reproduced only on latest MS Edge:
Microsoft Edge 41.16299.15.0
Microsoft EdgeHTML 16.16299
Do you have any ideas how to fix these issues? Any help is appreciated.
Thank you!
5 Answers, 1 is accepted
We have tested the cases and here are the results:
Case 1: We confirm that issue and we have logged it in our Telerik Ajax Feedback and Ideas portal: Cursor is moved right when an invalid symbol is inserted in MaskedTextBox in Edge 40+. You can subscribe to the portal item and get notified when there is any progress on the issue.
Case 2: We were able to replicate this after some continuous entering of symbols on a weaker virtual machine with the latest Edge. We have logged it also in our Feedback and Ideas portal: Page hangs sometimes when continuously entering input fast in MaskedTextBox in Edge 41.
Currently, we are unable to provide any feasible workaround for either of the issues. If we manage to find such, we will share it in the respective Feedback portal item.
As a token of gratitude for reporting us these issues, we have updated your Telerik points.
Regards,
Peter Milchev
Progress Telerik
Rank 1
Hello,
we see similar issue after upgrade to latest dll 2018.1.117 in Edge browser. Please make urgent fix or provide workaround to community.
Best regards
We have increased the priority of the internal feedback item. Unfortunately, we are still unable to provide a workaround for the issue.
If we manage to come up with a workaround, we will share it in the Feedback portal item so that it is available for the community.
Regards,
Peter Milchev
Progress Telerik
Rank 1
Hi Everybody,
Since Microsoft is going to replace the MS Edge engine with the Chromium one on January 15, 2020, where this problem does not exist, we changed the status of the bug report to completed.
You can find more details at Getting your sites ready for the new Microsoft Edge and to download the latest MS Edge Beta build from here.
Regards,
Rumen
Progress Telerik