Duplicated
Last Updated: 07 Jun 2024 18:57 by Jonathan
Alexander
Created on: 27 Jul 2023 11:41
Category: ComboBox
Type: Bug Report
5
AllowCustom: characters are lost during fast typing

When the option "AllowCustom" is enabled for a TelerikComboBox and the user types something above a certain speed, typed characters are lost. Here is a GIF showing the problem on the page https://demos.telerik.com/blazor-ui/combobox/custom-values – I typed "123456", but end up with "1246" instead. In between the input field is showing some weird glitching.

Is there a way to have the TelerikComboBox behave normally, as it apparently did in versions prior to 4.3.0? We noticed this behavior only some time after upgrading from version 4.0.1, where everything still works properly.

Duplicated
This item is a duplicate of an already existing item. You can find the original item here:
6 comments
Jonathan
Posted on: 07 Jun 2024 18:57
Setting DebounceDelay=0 doesn't solve the problem for me, though it does happen less frequently.
ADMIN
Georgi
Posted on: 19 Sep 2023 13:20

Hello, Anna,

I am sorry to hear that this issue is affecting your application. 

As of now, it is hard to give a concrete date for this bug fix, but there is a straightforward workaround in the meantime. 

The ComboBox has a DebounceDelay parameter which specifies the time between the last typed symbol and the updating of the Value. The default value of the parameter is 150ms. Setting DebounceDelay to zero will cause the Value to update immediately and prevent the characters from being lost during fast typing.

Regards,
Georgi
Progress Telerik

Stay tuned by visiting our public roadmap and feedback portal pages! Or perhaps, if you are new to our Telerik family, check out our getting started resources!
Anna
Posted on: 15 Sep 2023 11:34
Our application also suffers from this issue! Dear Telerik, when can we expect a fix?
ADMIN
Georgi
Posted on: 09 Aug 2023 13:38

Hello, Martin,

Thank you for sharing your point of view and how the defect affects your application. I have forwarded this to our management team in order to raise awareness and focus our efforts on fixing it in the upcoming releases.

Once again, thank you for your understanding and I apologize for the inconvenience this has caused.

Regards,
Georgi
Progress Telerik

Stay tuned by visiting our public roadmap and feedback portal pages! Or perhaps, if you are new to our Telerik family, check out our getting started resources!
Martin
Posted on: 07 Aug 2023 06:31
We already pointed out this problem in May of this year. On the one hand, it is understandable that the prioritization of implementations is based on votes. On the other hand, this is a very fundamental problem, which makes the component almost unusable when "AllowCustom" is activated. We are planning to release an application towards the end of the year where this component plays a very crucial role. Therefore I would like to ask again with emphasis to fix this problem in one of the next releases!
ADMIN
Georgi
Posted on: 28 Jul 2023 08:09

Hello, Alexander

Thank you for notifying us, this particular scenario has been brought to our attention already in the following thread. I have added your vote there as this helps us prioritize the fixes based on the community demand along with their severity. 

You can follow the thread in order to get updates about its status or if possible workarounds are found in the meantime. 

We apologize for any inconvenience caused until the issue is resolved.

Kind Regards,
Georgi
Progress Telerik

Stay tuned by visiting our public roadmap and feedback portal pages! Or perhaps, if you are new to our Telerik family, check out our getting started resources!