Completed
Last Updated: 14 Nov 2024 09:28 by ADMIN
Release 7.0.0
Martin
Created on: 25 May 2023 13:05
Category: MultiColumnComboBox
Type: Bug Report
22
Entering text quickly in the input field leads to the text blinking and becoming partially cleared.

The issue is reproducible when the `AllowCustom` parameter is set to `true`.
Typing rapidly in the input field of the MultiColumnComboBox component causes the entered text to blink. Also, some of the inserted symbols are cleared.

Reproduction (if bug)

Open this demo: https://demos.telerik.com/blazor-ui/multicolumncombobox/custom-values

Try to input text rapidly into the input field.

13 comments
Alexander
Posted on: 16 Oct 2024 07:47

Hello everyone,

what is the status of this? Can someone from Telerik confirm that this will indeed be in the version scheduled for November? We have been waiting for a fix for over a year now and it has been rescheduled multiple times.

Regards,

Alex

Alexey
Posted on: 19 Sep 2024 13:21
Version of Telerik where i find issue with TelerikComboBox

Alexey
Posted on: 19 Sep 2024 13:16
Hi,

When I try to use TelerikComboBox my text is jumping. How to fix it?
Look at example from your resource (https://demos.telerik.com/blazor-ui/combobox/custom-values) :
Link to video: https://drive.google.com/file/d/1k670qruMsfUez5QPN34bjYv2THWPY8Pk/view?usp=sharing

But when i try to use TelerikComboBox for real application with 120 data items, the text jumps even more and use TelerikComboBox for real data absolutely impossible.
Look at real app with TelerikComboBox in action:
https://drive.google.com/file/d/17R9POss9IvMIHITW5FzkyJ8Bh0NQSrkg/view?usp=sharing
ADMIN
Hristian Stefanov
Posted on: 11 Jun 2024 12:01

Hi Jonathan,

I confirm that this item has been rescheduled for our next Q3 release. The fix turned out to be more complex than anticipated and required additional time.

I apologize for any inconvenience this change in planning may cause.

Regards,
Hristian Stefanov
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!
Jonathan
Posted on: 07 Jun 2024 19:52

I'm still seeing this problem in ComboBox in v5.1.1 (February 2024 release). The DebounceDelay="0" workaround does not solve the problem for us.

Any updates?

ADMIN
Hristian Stefanov
Posted on: 19 Jan 2024 14:39

Hi Martin,

I understand the urgency, and I confirm that the specific date for the 5.1 release is planned for January 31st, as indicated by the "Planned" label on the public item. We look forward to the upcoming release, and I appreciate your patience until then.

Regards,
Hristian Stefanov
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: 18 Jan 2024 10:28

Hello Hristian Stefanov,

We had hoped that version 5.1 would be released in January. So far, however, nothing has happened. Is there already a rough date for the release? We really need this bugfix urgently.

Kind regards

Martin

 

Martin
Posted on: 30 Nov 2023 12:11
Thank you very much for this positive news. We are very much looking forward to the upcoming bugfix.

With best regards

Martin 

ADMIN
Hristian Stefanov
Posted on: 30 Nov 2023 09:04

Hi Martin,

I can confirm that the item is now planned for fixing in our next release, version 5.1.

Regards,
Hristian Stefanov
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: 23 Nov 2023 13:23
We have since released our application that uses this component. However, as this problem still exists, we had to implement a workaround before the release, which is not ideal. In the meantime, we have received the first customer inquiries in which our customers are complaining about the workaround. We would therefore like to insist once again that this bug is added to the official roadmap and fixed. 
ADMIN
Hristian Stefanov
Posted on: 18 Sep 2023 10:52

Hi Anna,

I apologize for the inconvenience caused by this issue.

Still, at present, the status of this item is "Unplanned," signifying that it does not currently have a specific timeline assigned. Nevertheless, as we prioritize and transfer the task to our short-term backlog, its status will be updated to "Planned" along with an associated release number. This release number will indicate the future release in which the fix is expected to be incorporated into our Blazor MultiColumnComboBox.

In the meantime, to ensure that you stay informed about any progress or changes regarding this item, I encourage you to subscribe to it. By subscribing, you will receive email notifications that provide timely updates on the status of the bug.

Regards,
Hristian Stefanov
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:33
Our application also suffers from this issue! Dear Telerik, when can we expect a fix?
Alexander
Posted on: 28 Jul 2023 08:07

We encountered this problem as well recently using the "TelerikComboBox" component. 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.

I am surprised to learn though, that this problem is known for two months now and nothing has happened, this ticked is still "Unplanned".

I compared the source code of `TelerikComboBox` for version 4.0.1 and 4.3.0 and found no differences there, that would explain the changed behavior. There are changes in the base component "ComboBoxBase", however, namely the introduction of a "private bool _shouldUpdateJsValue". This component is also the base component for "TelerikMultiColumnComboBox", so to me it is quite certain that these changes are causing the problem.

Could you please have a look at this problem and prioritize finding and implementing a solution? Thanks!