Autocompletion behaves differently for a couple of clients.

[Andrej]

Hello Telerik team,

 

we are using the RadAutocompleteBox in our .aspx-page. In the Page_Load-function we are binding the data like this:

protected void Page_Load(object sender, EventArgs e)
{
    var siteUrl = SPContext.Current.Web.Url;

    SPSecurity.RunWithElevatedPrivileges(delegate()
    {
        using(var site = new SPSite(siteUrl))
        {
            using(var web = site.OpenWeb())
            {
                var dbaccess = new DBAccess(web);

                radComboPlz.DataSource = dbaccess.GetPlzListeDataTable();
                radComboPlz.DataBind();
            }
        }
    });
}

With our control we want to enable the user to search for zip codes. This is how the control looks like:

<telerik:RadAutoCompleteBox RenderMode="Lightweight" runat="server" ID="radComboPlz" EmptyMessage="" Skin="Windows7"
    DataTextField="PlzOrt" InputType="Text" MinFilterLength="2" AutoPostBack="False" Filter="StartsWith">
    <TextSettings SelectionMode="Single" />
</telerik:RadAutoCompleteBox>

Now let's assume we have some zip codes looking like this, "509511", "509678", "509144"....

We also have some zip codes looking like this, "501223", "501789", "501445"...

The main difference is that some have 509 for the first three digits the others begin with 501.

Now the problem that we encounter is somehow hard to reproduce because only a couple of users are experiencing it. For example if I type 509 in most cases the suggestions are looking as supposed, namely showing entries starting with 509 (see attached file "509.png"). While for some clients the autocompletion seems to stop after "50" and therefor returns entries staring with "501" (see attached File "501.png").

We are using the latest version of IE but also were able to reproduce the issue using other browsers (FireFox and Chrome). Is this a know issue, if so how to handle it? Might we be missing some parameter in the Control?

 

Regrads and thanks in advance!

 

[Ivan Danchev]

Hello Andrej,

Since this is not a known issue we need to have it reproduced at our end, in order to further investigate what could be causing the behavior you described. Please isolate the AutoCompleteBox to a sample runnable project, attach it and post the steps needed for the issue to be observed.
Is the issue exhibited at your end when running any of our AutoCompleteBox demos?

Regards,
Ivan Danchev
Telerik by Progress