Thank you
9 Answers, 1 is accepted
Is there any workaround?
Hi,
This behavior is observed because of the latency of the SignalR connection and its async nature. Every keystroke goes to the server for processing (such as validation), and before a response comes back, another keystroke happens, and this causes such confusion. We are aware of this and we will see if anything can be done, and you can Follow the status of this task here (I have added your Vote for it): https://feedback.telerik.com/blazor/1422019-unable-to-show-all-typed-characters-in-textbox. The MS Issue linked from the article explains the situation in much more detail.
At the moment, there is no feature I can offer that will work around this. Changing the binding event is not available now, perhaps it might become possible through attribute splatting in the future (although I am not sure that it could be done, I have not tried), and the server code needs to execute for a variety of reasons. A WASM app would not have this issue, though.
The only other idea I can offer right now is to use a standard input and our styling for it: https://docs.telerik.com/blazor-ui/themes/form-elements#inputs.
Regards,
Marin Bratanov
Progress Telerik
UI for Blazor
Best regards,
Robert
https://github.com/aspnet/AspNetCore/issues/8204
Hi Robert,
Our components do more than just @bind-Value and in their fix they also exposed the @bind:event, which is not available on ours (yet). Our components need to execute server code when ValueChanged is to fire, which requires the C# code execution, which in a Server app has the latency and async nature described in the issue.
Regards,
Marin Bratanov
Progress Telerik
Hello Alan,
The issue with the lost characters has been fixed a long time ago: https://feedback.telerik.com/blazor/1422019-unable-to-show-all-typed-characters-in-textbox
If you do experience it again with the latest version, please open a ticket and send us a reproducible.
Regards,
Marin Bratanov
Progress Telerik
Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! Check it out at https://learn.telerik.com/.
Hello Alan,
The following article treats this, if reviewing it and the feature request it links, you have any questions, let me know: https://docs.telerik.com/blazor-ui/knowledge-base/textbox-validate-on-change
Generally, the server-side Blazor flavor is suitable for environments with very low latency, so this will not be an overhead. For other cases where lag is noticeable, WebAssembly is the better flavor.
Regards,
Marin Bratanov
Progress Telerik
Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! Check it out at https://learn.telerik.com/.