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

I would propose adding a floating label to the DatePicker element. When you have a form where all the other elements have floating labels and this single one doesn't, it really doesn't look good. So the option should be available the same as for other components. 

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

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/ 

Hi,

I'm trying to figure out how to persist and restore state in the native Vue grid.  Am I missing something; is this not available yet?

I found the article about doing it with the grid wrappers, but not native.

Thanks!

I'm submitting a...

• Bug report

Current behavior

The user cannot select a filter operator if the filter input doesn't have entered data.

Expected behavior

The user should be able to pre-select a filter operator no matter if there is data entered in the filter input or not.

Minimal reproduction of the problem with instructions

1. Open this StackBlitz example
2. In the Product Name column, I click the filter operator button
3. Select "Ends with"
4. Click the filter operator button again and see that "Ends with" is not selected.
5. Type "g" in the filter text field. Grid updates but doesn't filter the data by "Ends with" filter.
6. Click the filter operator button and see that "Contains" is selected instead of "Ends with"
7. Select "Ends with" once more and Grid filters correctly

I'm submitting a...

• Bug report

Current behavior

When the focused-date property of the Calendar is bound to data property, if you change the value of this property the focused date inside the component is not changing

Expected behavior

If the value of the focused-date property is changed, the new focused date should be applied in the Calendar

Reproduction

1. Open this StackBlitz example
2. Change the default focused date to the new one with a click on the "Change focused date" button
3. Nothing changes in the Calendar

I'm submitting a...

• Bug report

Current behavior

The labels of the Native inputs are not pronounced by screen readers like NVDA.

Expected behavior

The labels of the Native inputs should be pronounced by the screen readers.

Minimal reproduction of the problem with instructions

1. Open https://www.telerik.com/kendo-vue-ui/components/inputs/input/forms/
2. Start the NVDA screen reader
3. Select an Input field in the first example. The label of the selected field will not be announced.

Add Validation to the Kendo Vue native grid.

The pagination on the jquery grid is responsive by default with the ability to turn off responsiveness if desired. https://docs.telerik.com/kendo-ui/api/javascript/ui/grid/configuration/pageable.responsive

It would be useful to add responsiveness to the pagination on the Vue Native Grid with the same ability to turn it off if desired.

I'm submitting a Bug report

Current behavior

<chart :title-text="'Gross domestic product growth /GDP annual %/'" 
        :legend-position="'bottom'"
        :series-defaults-type="'area'"
        :category-axis-categories="categoryAxisData"
        :category-axis-major-grid-lines-visible="false"
        :category-axis-labels-rotation="'auto'"
        :value-axis-labels-format="'{0}%'"
        :value-axis-line-visible="false"
        :value-axis-axis-crossing-value="-10"
        :tooltip-visible="true"
        :tooltip-format="'{0}%'"
        :tooltip-template="tooltipTemplate"
        :theme="'sass'">
    <chart-series-item :name="'India'"
                        :data="indiaData"
                        :line-style="'smooth'">
    </chart-series-item>
    <chart-series-item :name="'World'"
                        :data="worldData"
                        :line-style="'smooth'">
    </chart-series-item>
    <chart-series-item :name="'Haiti'"
                        :data="haitiData"
                        :line-style="'smooth'">
    </chart-series-item>
</chart>

When using the ChartSeriesItem tags to define the data in the Chart component the following error appears in the console once the Vue project is started.

Expected behavior

<chart-series-item :name="'India'"
                        :data="indiaData"
                        :line-style="'smooth'">
    </chart-series-item>
    <chart-series-item :name="'World'"
                        :data="worldData"
                        :line-style="'smooth'">
    </chart-series-item>
    <chart-series-item :name="'Haiti'"
                        :data="haitiData"
                        :line-style="'smooth'">
    </chart-series-item>

Using a definition like the above, we should be able to define Chart's data with no issues.

Minimal reproduction of the problem with instructions

1. Open this project
2. In the console run "npm install"
3. In the console run "npm run serve"
4. Open the URL of the project and see the browser's console

I'm submitting a...

• Bug report

Current behavior

If a column has a value of 0 and there is no editor defined for this column, when editing Grids' data, the input in which 0 should be displayed is actually empty.

Expected behavior

When editing the Native Grid, the data displayed when a row is not in edit mode should be the same as when the same row is in edit mode.

Minimal reproduction of the problem with instructions

1. Open this StackBlitz example
2. Edit a row whose UnitPrice value is 0
3. See the empty input for the UnitPrice field, when the selected row is in the "edit" mode

I'm submitting a...

• Bug report

Current behavior

The "type" GridColumn prop is not available in the Typescript definitions available in the GridColumnProps.d.ts file.

Expected behavior

The type prop should be available also in the Typescript context as it is available in this Knowledge base article

I'm submitting a...

• Bug report

Current behavior

If the scrollable property of the Grid is set to 'null' the header of the Grid changes its background styles a column width, compared to when the property is not set.

Expected behavior

The styles of the Grid should not be changed when the scrollable property is defined.

Minimal reproduction of the problem with instructions

1. Open this StackBlitz example.
2. Remove the :scrollable="'none'" property definition from the Grid and see how it changes

I'm submitting a...

• Bug report

Current behavior

The value of the Native Input is updating the model after the input is focused out. It behaves as the lazy modifier is applied to it. The reported behavior is replicable only in Vue 3.

Expected behavior

The value of the model the Input is bound to should be updated on every user input as can be observed in this StackBlitz example.

Minimal reproduction of the problem with instructions

1. Open this StackBlitz project
2. Enter random symbols in the Input

The model is updated when you focus out the Input

I'm submitting a...

• Bug report

Current behavior

When the filterable property of the Native DropDownList is set to "true" the keyboard navigation is not working as expected. When the arrow up/down button is pressed in opened DropDownList, the selection in the popup is changed with two steps instead of one.

Expected behavior

On press of the up/down arrow key, the selection in the DropDownList's popup should be changed with one step, instead of two

Minimal reproduction of the problem with instructions

1. Open this StackBlitz example
2. Click on it to open the popup window
3. Press the arrow down key. The selection is moved to "Football" while the expected behavior is to move to "Basketball"

I'm submitting a...

• Bug report

Current behavior

readonly prop does not work in Autocomplete
https://stackblitz.com/edit/ertuag-b1ggo2?file=src/main.vue

Expected behavior

readonly prop does SDHOULD work in Autocomplete

I'm submitting a...

• Bug report

Current behavior

When the Date Inputs or DropDowns are positioned at the bottom of a page, their popup continues to open below the input field. This causes the popup to appear beyond the browser's boundaries, making the users unable to use the popup.

Expected behavior

The position of the popups of the Date inputs and DropDowns should be automatically changed based on the available space below each of the components. If there is not enough space to open the popup below the component's input, the popup should appear above the input.

Minimal reproduction of the problem with instructions

1. Open this StackBliz example
2. Click on the "Open in a New Window" button at the right corner
3. In the opened browser window, scroll to the bottom of the page
4. Open the popup of the DropDownList

I'm submitting a bug report

Current behavior

When the DatePicker popup calendar is opened on a device with iOS 14.1, once the navigation arrow is clicked, the pop immediately closes

Expected behavior

Tapping on the navigation arrow should change the current calendar view and remain the popup opened.

Minimal reproduction of the problem with instructions

1. Open this demo on a mobile device with iOS 14.1
2. Open the calendar of the DatePicker and navigate it with the navigation arrows