Describe the bug
The steps property is not used/read when set on the DateTimePicker component, even though it says it can on the docs.

To Reproduce

1. Open this StackBlitz link
2. Open the popup of the TimePicker. The steps are applied.
3. Open the popup of the DateTimePicker and select a random date
4. The TimePicker inside the DateTimePicker doesn't apply the definition of the steps property.

Expected behavior
The steps of the TimePicker, inside the DateTimePicker should be the same as those in the TimePicker component.
Screenshots

Describe the bug
When defining a custom editor Template for the Scheduler(wrapper) component we define the value passed to the editable-template property as follows:

editorTemplate(data: any): any {
  return {
    template: EditEventTemplateComponent,
    templateArgs: Object.assign({}, data, {
      parentComponent: schedulerRef.value,
    }),
  };
}

With the above definition, in the EditEventTemplateComponent, the templateArgs cannot be accessed inside the setup function, when the Composition API is used. In the mean time, the templateArgs are accessible in the template of the EditEventTemplateComponent.

To Reproduce

1. Open this project: sample-scheduler-composition-api.zip
   and install its NPM packaged(npm install)
2. Start the project(npm run serve)
3. Double click on one of the events available inside the Scheduler.
4. Check the console of your browser
   -->

Expected behavior
The templateArgs should be accessible inside the setup function when using Composition API.

• Possible workaround: Use the classic Options API instead. When we use the Options API, the templateArgs are accessible inside the mounted hook.

I want to use filterGroupByField to indicate that a column that has a GridColumnMenuCheckboxFilter.  Naturally, there can be more than 2 items selected.  If more than 2 items are selected, the filterGroupByField returns null.

See this example (select more than 2 product id's):

https://stackblitz.com/edit/i58xwv?file=src/main.vue

Describe the bug
When you use the filterGroupByField method, if there are more than 2 filtered items, the method returns null. If the filtered items are one or two, the method works correctly.

To Reproduce

1. Open this StackBlitz example
2. Open Browser's console(F12)
3. Click on the "ProductName" column menu and select 3 or more checkboxes
4. See the output in the console which is "null"

Expected behavior
The result returned from the filterGroupByField method should be with a structure similar to the below one, no matter how many checkboxes have been selected in the column menu.

Currently, the Kendo UI for Vue Native DropDownList doesn't have the valuePrimitive property which is available in the:

• Angular DropDownList - https://www.telerik.com/kendo-angular-ui/components/dropdowns/api/DropDownListComponent/#toc-valueprimitive 
• and the jQuery DropDownList - https://docs.telerik.com/kendo-ui/api/javascript/ui/dropdownlist/configuration/valueprimitive 

Providing such property for the Native Vue DropDownList will be useful in different use-case scenarios. 

Describe the bug
The messages from the cldr-dates-full library are not loaded correctly in the Calendar component.
Month names in the Calendar control in Polish language should be in the nominative case.
Tooltips for the days in the calendar are in the genitive case and they are correct.

• The same issue could be replicable in other languages.

To Reproduce
Steps to reproduce the behavior:

1. Open this example.
2. See the translation of the month in the Calendar

Expected behavior
The month's name should be "listopad 2021". Instead, it is "listopada 2021". For reference, check this sample that uses the Kendo UI for jQuery suite and the messages are correct.

Screenshots

If a date column has a GridColumnMenuFilter, the filter drop down closes as soon as you attempt to open the date. 

Reproduction steps:

Add a GridColumnMenuFilter to a column that is defined as a date.  Upon opening the filter and attempting to select a date, the filter immediately closes.  

This example has the problem reproduced. https://stackblitz.com/edit/zdmtjk?

In a scenario when a mouse is connected to an iPad, using the mouse, we cannot switch the states of the Switch component.
If the screen is touched, the Switch is correctly switching position.

Here is a video demonstrating the issue:
kendoswitch-rpreplay-final1635815724-mp4.zip

Hi,

I need to fill and AcroForm PDF. I want to load the pdf and fill it from input fields in kendo vue, when I am done I need to send the pdf back to server or download/print the filled out pdf. 

In this example the 'expanded' prop is set to true by the filter is not expanded - https://stackblitz.com/edit/uquwh8-1e5npd?file=src/ColumnMenu.vue

a possible workaround - uncomment the line in the mounted function.

Add functionality that allows the users to configure the Native Grid's Pager in a way it has the "All" option in its page sizes DropDownList.

The "All" option is available in the Kendo UI for jQuery suite(check the second example on the page). When the "all" option is selected, all Grid records are loaded on one page.

It will be a nice feature if the Native Grid can support a row selection through the keyboard. 

Example scenario:

1. Click on a checkbox in the Grid and select a row
2. Hold the Shift or Ctrl key and press Arrow up or arrow down button

Targeted result: With the press of an arrow button, the row above or below gets selected

Here is a sample project that demonstrates an implementation similar to the targeted one.

The Kendo UI for Vue Scheduler Wrapper doesn't support year view which is available in the jQuery suite.

To reproduce the issue follow the below steps:

1. Open this StackBlitz example
2. From the DropDownList in the upper right corner select "Year"
3. Check the console. The following error appears in it:
   

Expected behavior
The "Year" view should be available in the Kendo UI for Vue Scheduler Wrapper

A warning appears in the console when the Open and Close events of the ComboBox are triggered.

Example: https://stackblitz.com/edit/v8hk4y?file=src/main.vue

Bug report:
https://stackblitz.com/edit/bbuqh1?file=src/main.vue

Steps:
Focus the input, type some text and blur -

Current:
an warning is observed in the console and the types string is passed to the change event.

Expected:
an warning is observed in the console and the types string SHOULD NOT BE passed to the change event.

The Native NumericTextBox doesn't have the 'k-state-focused' class applied to it, once the component is focused. 

For comparison, the Angular and React versions of the same component get this class applied.

React: https://www.telerik.com/kendo-react-ui/components/inputs/numerictextbox/ 

Angular: https://www.telerik.com/kendo-angular-ui/components/inputs/numerictextbox/ 

Currently in Vue we don't provide the ability to share with the customers the source code before the compilation but just the already compiled code.

We need to provide the ability to fork the repository and build components from the Vue repository similarly to the way it is done in Angular and React.