Declined
Last Updated: 29 Oct 2020 07:58 by ADMIN
Created by: Seven Spikes
Comments: 1
Category: AutoComplete
Type: Bug Report
0

On Android mobile devices (probably on other mobile devices as well) the click event from the drop-down list popup triggers the click event of controls below the clicked item.

The issue is similar to this one described here - https://www.telerik.com/forums/dropdownlist---click-through-issue-on-android-mobile-device

We managed to reproduce it including kendo.all.min.js and also including only the individual components required for the autocomplete to work.

In your demo, we simply added a button below the autocomplete and show an alert when the button is clicked.

Here is a DOJO link with the individual components:

https://dojo.telerik.com/azAFINIz/9

Simply type "A" so that the list of countries is shown and then click on "Andorra" and the button below the list will also be clicked.

The same DOJO link with kendo.all.min.js takes some more steps to be replicated.

https://dojo.telerik.com/ezuBaMEF

Here you need to type "A" and click on "Andorra", it won't fire the click event of the button initially but if you delete the selected items and type "A" again and then select "Andorra" the button will be clicked.

We have seen the same issue in version 2020.1 as well.

I workaround for this issue will be much appreciated!

Completed
Last Updated: 27 Oct 2020 13:45 by ADMIN
Release 2020.R3.SP.next
Created by: Jason Feng
Comments: 1
Category: AutoComplete
Type: Bug Report
0
Hi, I think this is a bug with AutoComplete widget. The document says the highlightFirst default is true, which means I don't need to specifically define it. In reality, I have to set it as true in order for it to work. Please verify.
Unplanned
Last Updated: 29 Jun 2020 06:20 by Sascha

Bug report

When using the AutoComplete with the suggest configuration set to true and separators configuration is set to an Array of characters additional garbage characters are added to the input when the user starts typing

Reproduction of the problem

  1. Run this dojo
  2. Start typing

Current behavior

Additional characters are displayed
image

Expected/desired behavior

No additional characters should be displayed.

Environment

  • Kendo UI version: 2020.2.617
  • Browser: [all]
Completed
Last Updated: 25 Feb 2020 12:58 by ADMIN

When user inputs text that does not match any of the items in the data source and presses the down arrow key, the "suggestions" drop down list opens up with an empty list when the configuration option is: 'noDataTemplate: false'.

 

This seems to be a regression since it appears to be working in an older version:

Thread: https://www.telerik.com/forums/is-it-possible-to-disable-nodatatemplate

Demo for suggested fix: http://dojo.telerik.com/EXEnu

Note the kendo version (2016.3.914).

 

Same demo with newer version of kendo (2018.2.620): http://dojo.telerik.com/ehaDEsIq

 

Reproduction steps:

1. Type a string in the AutoComplete that does not match any values in the data source, e.g. ("123")

2. Press the "down" arrow key to open up the suggestions dropdown.

The suggestions dropdown opens up with no items -- it should not be opening up at all.

 

Behavior in (2016.3.914) is that the dropdown does not open when using the arrow keys if the typed in text does not match any of the items in the suggestions list. [Correct]

Behavior in (2018.2.620) is that the dropdown does open with an empty list when using the arrow keys if the typed-in text does not match any of the items in the suggestions list. [Incorrect]

Unplanned
Last Updated: 25 Feb 2020 12:56 by ADMIN

If I have a min length of 3 and enforceMinLength set to true, if you enter in 3 or more characters and then start deleting them (keyboard) once you get below the min length the dropdown remains open when it should close.

 

See the dojo option under the enforceMinLength API documentation for a sample to test.

 

 

 
Completed
Last Updated: 10 Dec 2019 07:53 by ADMIN
Created by: Marcin
Comments: 1
Category: AutoComplete
Type: Feature Request
0
Currently autocomplete searches after each character entered, which can have big impact for large result sets. When user type fast 3 chars there is no need to search 1,2,3 just 3. So it would be beneficial to allow setup some delay 200-300 milliseconds for search.