"@progress/kendo-vue-dropdowns": "^3.5.0",

"vue": "^3.2.13",

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 we have a multi-level nesting in the data loaded in the Native TreeView the parent nodes that are below level0 are not displayed correctly when set as expanded.

Sample TreeView structure
|-Level0
-|-Level1
--|-Level2
---|-Level3

• The issue is replicable when the "animate" prop of the component is set to "true". If "animate" is set to "false", the TreeView is displaying all its nodes as expected.
• The issue is replicable when the processTreeViewItems method is used. If the TreeView is directly bound to an array, the component is working correctly. See this example.

To Reproduce
Steps to reproduce the behavior:

1. Open this StackBlitz project
2. See nodes "Item1.2" and "Item2.3"

Expected behavior
The "Item1.2" and "Item2.3" nodes should be expanded and their child nodes should be displayed by default as in this example.

Screenshots

Describe the bug
The position of the DropDownList's popup is not updated when the popup is opened above the component and the data items in the popup are filtered.

To Reproduce

1. Open this StackBlitz example in a new tab
2. Resize the browser's window in a way the DropDownlist is at the bottom of the visible area and click on the component to expand its popup. Because there is no space below the DropDownList, its popup should pop above the component
3. In the search box in the popup write "sm"

Expected behavior
The bottom of the popup should be constantly stuck to the DropDownList and not staying at it initial position above the compoennt.

Screenshots

Describe the bug
The rowReorder event is missing in the Wrapper Grid component, while it is available in the Kendo UI for jQuery Grid. Currently, the only way the event can be used is by using a code like the below in the mounted hook of the Vue app:

    var grid = this.$refs.grid.kendoWidget();
    grid.bind('rowReorder', function (e) {
      console.log('row', e);
    });

Expected behavior
The rowReorder event should be available for usage as the other events of the Wrapper Grid

Describe the bug
The DropDownButton's itemClick event doesn't work when you select one of its items with a tap on a touchpad.

To Reproduce

1. Open this StackBlitz example
2. Expand the DropDownButton and select an item with a mouse click - the itemClick event is logged in the event logger
3. Using a touchpad, select an item by tapping on the touchpad.
4. See the event logger - the itemClick event is not logged

Expected behavior
The itemClick event should be triggered consistently no matter if a mouse click or touchpad is used

Vue Version: 3.2.37

@progress/kendo-vue-layout version: 3.5.1

When using TabStrip in Vue 3 with the Composition API and `<script setup>`, there cannot be anything inside of the TabStrip other than visible markup. If there is an HTMLnode that's a comment, or is hidden using a `v-if,`, then that part of the page will not render and throw an error.

This is the error received:
"`Uncaught (in promise) TypeError: children.forEach is not a function`" quoting a utils.js file line 4.

If my TabStripTabs have a v-if on them to not show if data isn't available for them, then the whole section of the page isn't useable.

Describe the bug
When having a scenario of Native Grid with a paging functionality, the pageChange event is being triggered when there is an interaction with the UI of the Pager.

When the user selects the number of rows per page, by choosing this value from a DropDownList, the object available in the event handler of the pageChange event has a value for its event property.

When the pageChange event is triggered by a change in the pages (1, 2, 3, etc.) the mentioned above event property has a value of undefined inside the event handler.

To Reproduce

1. Open this StackBlitz example
2. Change the number of items per page to 20.
3. Change the Grid page by using the page numbers
4. Check the browser's console

Expected behavior
The event prop should be defined no matter which element is triggering the pageChange event.

• Bug report

Current behavior

https://stackblitz.com/edit/mt45fg-d8vmdm?file=src/main.vue

The popup is Not appended to the div provided

Expected behavior

The popup is appended to the div provided

Describe the bug
The appendTo and className properties of the Popup component cannot be set for the DropDowns, when configured through the popupSettngs prop.

To Reproduce

1. Open this StackBlitz example
2. Expand the DropDownList

Expected behavior
We should be able to add a className to the component's popup and control the element to which the popup will be appended to.

Describe the bug
The unit tests of a custom avatar component, which uses a Kendo UI for Vue Native Avatar are failing due to a problem with the license validation. This issue happens after upgrading the Kendo UI for Vue components from 3.5.0 to 3.5.1.

To Reproduce
Steps to reproduce the behavior:

1. Download this project and extract it
2. Run "yarn"
3. Run "yarn test"

Expected behavior
The tests should run correctly in version 3.5.1 as they used to be with version 3.5.2

Screenshots

Describe the bug
When the Native DropDownList is configured to work in a data virtualization mode, if the user scrolls to the last data page, then close and reopen the popup of the component, no data is visualized in the popup. If the empty popup is scrolled, then the missing data appears back.

To Reproduce

1. Open this StackBlitz example
2. Open the DropDownList and scroll its data to the end
3. Click outside the DropDownList to close its popup
4. Click on the DropDownList to open it

Expected behavior
The same data that is visible before the popup is closed, should be visible inside the DropDownList when it is opened on step 4 above.

Screenshots
When step 4 is done:

When the popup is scrolled:

Describe the bug
When we use the Native Grid with a sortable configuration set to "{ mode: 'multiple' }" and we have a ColumnMenu, once the sorting functionality of the column menu is used, the sorting is reset.

To Reproduce

1. Open this StackBlitz example
2. Apply sort to the Name and Unit Price columns by clicking on each column header.
   
3. Select the column menu of the Discounted column and click the sort Ascending or Descending button.
   
4. Notice that the previous nested sort applied in the above steps is cleared and only the Discontinued column has an applied sorting.

Expected behavior

The sorting shouldn't be reset no matter which Grid sorting functionality is used. In the above example, the sorting of the Discontinued column should be added to the complex sorting.

hhttps://stackblitz.com/edit/kgeavu?file=src/main.vue

the console.log is observed even when selecting other tabs.

Describe the bug
When having a movable Native Window component with a Grid inside it, the more cells(rows and columns) the Grid has, the slower the Window's rendering is. This effect is not replicable in the Kendo UI for jQuery scenario.

To Reproduce

1. Open this StackBlitz example that has a Native Window + Grid implementation
2. Open this Dojo example that has the same scenario as in point one but using the Kendo UI for jQuery suite
3. Start to move the Window components in both examples
4. Compare the way the Window is rerendered

Expected behavior
The rerendering of the Kendo UI for Vue Window should be smooth as it is in the Kendo UI for jQuery Window demo

Describe the bug
The layout of the column menu popup window, inside the Native Grid, is different when using version 4.x.x and version 5.x.x. of the Kendo Themes.

• The issue is replicable with all Kendo Themes

To Reproduce

1. Open this example
2. Click on the column menu of the Name column
3. Inside the column menu, click on "filter"

Expected behavior
There should be a space between the different elements in the column menu -> filter popup

Screenshots

Describe the bug
In a scenario of Native Grid with Filter row once the filter popup is opened, the only way we can close it to select a value from the dropdown.

To Reproduce

1. Open this StackBlitz example
2. Click on the icon next to a random input in the filter row
3. Click outside the popup that appears in step 2.

Expected behavior
The popup of the filter should be automatically closed when it is blurred.

Screenshots

Describe the bug
When the PageChange event of the Native ComboBox or MultiSelect is triggered the following warning appears in the browser's console:

To Reproduce

1. Open this StackBlitz example
2. Expand the popup of the MultiSelect and start scrolling its items
3. Check the browser's console

Expected behavior
There shouldn't be any browser warnings when the pagechange event is triggered

Describe the bug
Both the ComboBox and DropDownList don't work as expected when configured in a virtualization scenario. The issue is related to skip value available in the event handler of the "pagechange" event. When you scroll the virtualized list down and then start to scroll in back in the upside direction, the value available in the event.skip property is at first being changed to a number that is bigger than the current "skip" value.

The result is that if you are currently at element 5000 in the popup list, and decide to scroll in the upside direction, the list will display items with an ID bigger than 5000 and the scroll in the upside direction will start from this new position.

To Reproduce

1. Open this StackBlitz example
2. Open your browser's console
3. Scroll fast to an item with ID of 2000 +
4. Start scrolling up to item 0
5. See the skip values in the console.

Expected behavior
When scrolling the items in the ComboBox or DropDownList components, the lists should behave the same way no matter if they are configured in a virtualization or default scrolling mode. When the list is scrolled, its items should move up or down without jumping to records that are not in the same direction as the scrolling.

Screenshots
If applicable, add screenshots to help explain your problem.

Describe the bug
In a Server-side rendering scenario, the tab navigation of the Native TabStrip is not visible right after its load. The tab navigation is not visible until the page gets rehydrated on the client side.

To Reproduce

1. Open this StackBlitz example
2. Reload the result pane a few times

Expected behavior
The tab navigation should be visible right after the page load, not when the page gets rehydrated on the client side