It appears the taglist always requires a selected tag to be present in the dataItems. However this tag is not gonna be present in the dataItems when a filter is applied. It seems this causes an error, where the taglist tag expects to be able to find its corresponding dataItem in the dataItems

Repro:

1. Open stackblitz and select 'large'
2. filter on 'L'
3. observe no runtime error in console
4. remove 'L' filter and replace it with 'M'
5. see a runtime error in the console

https://stackblitz.com/edit/z7ejuk?file=src%2Fmain.vue

I know a quick workaround for this is to ensure a selected tag is always added to the filtered dataItems, preventing the error. But are there perhaps other workarounds or is this something that can be fixed in a future release?

Thanks in advance

Hi Team,

KendoNative Multiselect which is configured to work with primitive values has issue with filtering

PFB link below for the demo

https://stackblitz.com/edit/habvwq-e4ahdk

Describe the bug
The items inside the popup of the Multiselect are not correctly visualized when scrolling the data. The issue can be easily observed in scenarios where the page size and the total of records are close numbers.

The issue is that while scrolling, the Multiselect scrolls but the actual contents of the popup don't move until the scroll bar is more than halfway down.

To Reproduce

1. Open this project
2. Start scrolling the items in the MultiSelect

Expected behavior
With the move of the popup scroller down, the data should be scrolled too, no matter if the scroller has reached its middle position or not.

Screenshots
The screenshot is from the linked above example. The items displayed in the popup window should be around "Item 50"

Describe the bug
When using the listNoDataRender prop of the Native MultiSelect component the following warning appears in the browser's console.

To Reproduce

1. Open this StackBlitz example
2. Open the browser's console

Expected behavior
No warnings or errors should appear in the dev console

Describe the bug
The MultiSelect component throws a console error when a text value is entered in its input and the component is used as a part of the Native Form.

The issue is replicable only when a text is entered in the component's input. Everything works as expected if a value is selected from the MultiSelect's popup list.

• A possible workaround for the bug is demonstrated in this StackBlitz project.

To Reproduce

1. Open this StackBlitz example
2. Enter random text in the MultiSelect's input
3. Open the browser's console and see the following error

Expected behavior
No errors should appear in the browser's console when using the MultiSelect component as a part of the Form component, no matter the specific configuration of the MultiSelect.

In some scenarios, we need to display the selected MultiSelect values as comma-separated values and not as chips.

Currently, the displaying of comma-separated values can be achieved using a custom template similar to this one but providing a property that can configure this behavior out of the box will be a very useful improvement in the component. 

It could be useful to have a prop or some way to set focus on the component. The concrete scenario is about the multiselect but it could also be added in other components.