C1TextBox Debouncing

C1TextBox Debouncing

Posted by: siniawski.jj on 21 January 2025, 6:18 pm EST

• 

  siniawski.jj

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 21 January 2025, 6:18 pm EST

  Hi,

  I am using a Server Side Blazor app and seeing issues with Text Input Stuttering and losing characters due to the latency between the client and server. This should be fixable with debouncing as I have seen other input component libraries implement. Is debouncing on the list of features to implement?

  Thanks

• 

  ankit.kumar

  

  • Post Options:
  • Link
    Copy

  Posted 22 January 2025, 3:26 am EST

  Hi,

  I have escalated this to the concerned dev team on the scope of debouncing in the C1TextBox. The internal tracking id for the same is: C1XAML-37662. I will let you know once there is more information on this from the dev team.

  You could also use another event for binding with “@bind:event”. You could use the following code snippet to listen to “FinishedTextChange” instead of “TextChanged” (i.e., on focus lost when text was changed.)

  <C1.Blazor.Input.C1TextBox @bind-Text="textString" @bind-Text:event="FinishedTextChange"  />

  For more information, you could refer to the following forum case: https://developer.mescius.com/forums/blazor-edition/c1textbox-and-bind-text-issue

  Regards,

  Ankit

• 

  ankit.kumar

  

  • Post Options:
  • Link
    Copy

  Posted 27 January 2025, 7:36 am EST

  Hi,

  The developers have mentioned that the issues related to the binding of the C1TextBox (related to loosing characters and latency) will be resolved in the 2024 v2 hotfix 2 (expected released by Mid of March 2025).

  Further, I will let you know when the build is available.

  Regards,
  
  Ankit

• 

  siniawski.jj

  • Post Options:
  • Link
    Copy

  Posted 28 January 2025, 2:43 pm EST

  Hi Ankit,

  Thank you for the update! I look forward to Hotfix in March.

  Thanks,
  
  Justin

• 

  ankit.kumar

  

  • Post Options:
  • Link
    Copy

  Posted 3 April 2025, 12:19 am EST

  Hi Justin,

  The reported issue has been resolved in the latest version of the C1 Library. I have tested it with version 8.0.20242.1038, and it appears to be working fine on my end.

  Please upgrade to the latest version and let us know if you still encounter the issue.

  Regards,

  Ankit