Currently, the Native Grid implementation doesn't provide an option for the implementation of the scenario from the following screenshot. 

The thing that can be currently customized in the grouping toolbar of the Native Grid is only its text. 

Please provide an option by which we can define a custom template for the grouping toolbar.

We've been using the Telerik UI for ASP.NET AJAX Scheduler for years.  It has this nice reminder dialog that can be checked on this link and the below screenshot. 

Can you add the Reminder functionality in the Native Scheduler component?

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

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.

Currently, the different Kendo UI for Vue Native Inputs have the label property that adds a Floating label to the selected component. By defining a Floating label, the only way we can position it above the selected Input is to enter a value in the input. 

The current request is about an option that allows the developer to set the position of the Floating label above the Input, no matter if there is or isn't a value in the component.

Currently, this functionality can be achieved using the following CSS. However, it will be easier if we can control the label position with a single prop

.k-floating-label-container.k-empty > .k-label {
  top: 0;
  left: 0;
}

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.

It will be a very nice feature improvement for the Menu if we can add a custom class to the popup of each menu item. Such a feature will allow us to easily customize the look of the popup itself, edit its position, etc.

The popup class can be configured using a property like "popupClass" or something else. 

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
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.

The current implementation of the Native TreeView doesn't allow you to customize the expand/collapse arrows of the component. 

Can you please provide a property that allows the definition of a custom class for a given TreeView group? Being able to define such a class, using CSS we can easily control the look of the different elements of each TreeView group.

With the current implementation of the Native Grid, if one needs to set a minimum width to a column that needs to add the implementation suggested in this Setting a Minimum Column Width example.

While the approach in the above example works as expected, the logic that needs to be added can be internal for the Grid component. Thus the users will have to add a simple column property like the below and no other configuration should be set.

  {
    field: "ProductName",
    title: "Name",
    minWidth: 200
  }

Describe the bug
By default, the Dialog component is a modal window. This means that once the Dialog appears, the page elements are the only ones the users can interact with.

Currently, if you use the keyboard navigation functionality of the Dialog, after pressing the Tab key multiple time, the focus will be on the "Open dialog" button below the modal. This should not happen.

To Reproduce

1. Open this StackBlitz example
2. Click on the "Open in new window" button to open the example in a separate window/tab
3. In the new window, click on the "Open dialog" button
4. Once the Dialog is opened, press the Tab button 8 times and press Enter
5. The Dialog will be closed because, after the 8th Enter press, the focus will be again on the "Open dialog" button below the modal area.

Expected behavior
When using the keyboard navigation of the Dialog component, the focus shouldn't be transferred to the elements below the modal area. It should be kept among the elements that are displayed in the Dialog.

Describe the bug
The DatePicker component behaves unexpectedly when it is part of an HTML form that has a Submit button. The things that happen are as follows:

1. If you focus the DatePicker and press Enter, the popup of the component opens
2. If there are two DatePickers inside the HTML form, focusing on the second DatePicker and pressing Enter, opens the popup of the first DatePicker

To Reproduce

Scenario 1:

1. Open this project
2. Focus the DatePicker and press Enter

Scenario 2:

1. Open this project
2. Focus on the second DatePicker and press Enter

Expected behavior
When pressing Enter inside the HTML form, the form should be submitted and no DatePicker popups should open

The Vue native ComboBox and Autocomplete do not support the value-render prop and slot, so a selected value cannot have a custom display. The DropDownList does however - they should all be consistent in this.

DropDownList reference:
https://www.telerik.com/kendo-vue-ui/components/dropdowns/dropdownlist/custom-rendering/#toc-values

Currently, the Native DatePicker component doesn't allow you to control out of the box if a given date should be enabled or disabled for selection. 

Providing a property for controlling the enabled/disabled Calendar dates will be very useful for the functionality of the DatePicker component.

Describe the bug
When using a slot template inside the Grid, the content of the template should always have only one DOM element on the root level. If there are multiple elements on the root level, only the first element will be rendered.

In scenarios when we add a comment inside the slot template as a first element, the Grid recognizes it as the first element in the template and nothing will be rendered.

To Reproduce

1. Open this StackBlitz example
2. See the Unit Price column

Expected behavior
The rendering of the slot template shouldn't depend on the number of root elements inside it. The template should be rendered in scenarios with both single and multiple elements in the root.

Screenshots