When using AutoCompleteBox with IME, the AutoCompleteBox may "steal" characters from the IME input.
For example, if there is an auto complete entry named "Hello", and we type "HA" in the AutoCompleteBox with an IME, the initial character "H" will be stolen by the AutoCompleteBox, leaving only "A".
6 Answers, 1 is accepted
I tried to replicate the issue you described in the examples available in our WPF Controls Samples application and the SDK Samples Browser, but was, unfortunately, unable to do so.
Could you please try replicating the issue in any of these examples as well and let me know if you succeed in doing so? If that is the case, please specify the exact demo which demonstrates the issue as well as the action steps which are required in order to observe it.
Thank you in advance for your cooperation on the matter.
Thanks for your reply.
I can confirm that this issue only exists when the AutoCompleteMode is set to Append or SuggestAppend. Setting it to Suggest, as the examples in the SDK Samples Browser do, will not have any problem dealing with IME.
Thank you for the clarification.
I tried setting the AutoCompleteMode of the RadAutoCompleteBox in the Data Validation demo from our SDK Samples Browser to Append and SuggestAppend, but the characters seem to correctly be displayed by the control. I've attached a short recording of the result I observe at my end to my reply for your reference.
Could you please have a look and let me know if I'm missing something of importance? I will be awaiting your reply.
Please try to type something starting with "T" with IME in the Data Validation demo. The first character typed into the IME will only be stolen if the RadAutoCompleteBox has one or more items with a matching initial (in this demo, it only has items with an initial "T").
Thank you for the clarification. Indeed, I was able to replicate the behavior at my end after following the actions steps you specified.
After looking at the source code, however, I can state that the control is not designed to work with IME input as it relies on the KeyDown event which is not fired when using this input mode. I have thus logged the following feature request in our feedback portal on your behalf regarding such support. I have also awarded you with some Telerik points for bringing this to our attention.
If I can further assist you in any other way, please let me know.