Currently, the Native TabStrip component doesn't provide the option to make its tabs scrollable. 

Making TabStrip's tabs scrollable is useful for scenarios with smaller screen sizes.

Once the request is implemented, we should have something like this:

Describe the bug
The Native Signature component throws the following error when its popup is minimized:

To Reproduce

1. Open this StackBlitz exmaple
2. Open the popup of the Signature component
3. Check the browser's console where the above error will appear
4. Close the popup
5. The above error appears for a second time inside the console

Expected behavior
There shouldn't be any errors when opening/closing the popup of the Signature component.

Describe the bug
The value of the data-grid-row-index attribute of the different Native Grid rows is always -1, no matter the scenario in which the component is used.

To Reproduce

1. Open this StackBlitz example
2. Inspect a random Grid row and see its attributes

Expected behavior
The different rows inside the Grid should have different values for the data-grid-row-index attribute.

Describe the bug
With the current Upload implementation, the component doesn't provide an option to filter the files that are selected for upload if the auto-upload property is set to true.

Currently, the files can be filtered only if the auto-upload is set to false as in this StackBlitz example.

To Reproduce

1. Open this StackBlitz example with auto-upload property set to true
2. Select multiple files + one that has the letter "g" in its name

Expected behavior
The file with the letter "g" should not be uploaded

• As a possible solution for the issue, we can provide an event that is triggered before the file upload and when the event is triggered, the files will be filtered.

Describe the bug
There is a blank space at the bottom of the Grid when the user scrolls the data. This blank space appears on a specific configuration where the Native Grid is configured with virtual scrolling and the groupable property is set as follows:

:groupable="{ footer: 'visible' }"

• The issue is replicable in both Vue 2 and Vue 3
• The issue is not replicable if the groupable prop is defined like this:

:groupable="true"

To Reproduce

1. Open this StackBlitz example
2. Scroll the data items to the bottom of the Grid

Expected behavior
There shouldn't be any white/blank spaces at the bottom of the Grid

Screenshots

Describe the bug
The TreeListDataStateChangeEvent type currently has the following props:

• component, dataState and event

While its props should be:

• component, data and event

Expected behavior

The types defined in the TreeListDataStateChangeEvent should be component, data, and event

Currently, the Native Scheduler doesn't provide an option to programmatically display its "Add new event" or "Edit event" form. 

In some scenarios, it will be useful to have the option to programmatically display the "new event" form or be able to load the data of specific existing event into the editing form 

Describe the bug
The Native Tooltip is not hiding when the mouse cursor is moved fast from the target element in the direction where the Tooltip is about to appear.

To Reproduce

1. Open this StackBlitz
2. Hover the Button and move fast the mouse cursor to right(covering the area of the Tooltip)
3. Repeat step 2 multiple times if the Tooltip hides

Expected behavior
The Tooltip should disappear when the mouse cursor is moved away from the target element no matter the direction in which the cursor is moved.

Screenshots

Currently, the Native Scheduler component doesn't provide the option to group its date by date. 

This option is available in the Kendo UI for jQuery and it will be really nice if we have it also in the Native Vue Scheduler.

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
A licensing warning may continue to appear in the browser's console, no matter whether the licensing activation has been successful or not.

The issue is replicable when the user trying to activate a license has had an active license in the past and this license is already expired.

To Reproduce
Because of the specifics of the issue, a project in which the bug can be replicated won't be publicly provided.

Expected behavior
The license activation process should activate one's license no matter the previous licensing history of the user

Describe the bug
When the Grid's resizable property is set to true, the following test fails:

import { describe, it, expect } from "vitest";
import App from "../App.vue";
import { render } from "@testing-library/vue";

describe("App.vue", () => {
  it("renders apps", async () => {
    render(App);
  });
});

• The issue is not replicable if in Draggable.js file the:

import KendoDraggable from '@progress/kendo-draggable';

is changed with:

import { Draggable as KendoDraggable } from '@progress/kendo-draggable';

With this error:

To Reproduce

1. Open this project
2. Run 'npm install'
3. Run 'npm run test:unit'

Expected behavior
The test should pass as it used to pass in version 3.5.0, for example.

Describe the bug
When activating the keyboard navigation inside the Native Grid and there are custom cells in this Grid, the navigation between the cells(in a specific scenario) is slow.

Scenario: In a Grid whose cells are all custom, focus a random cell in the first column. Then press and hold the right keyboard arrow. The focused cell starts moving to the right and then freezes until the last Grid column is reached.

Here is a video demonstrating the described scenario: https://user-images.githubusercontent.com/41293735/202707680-1964d01e-dbd3-4a35-93c4-1dbcfd45e887.mp4

• The issue is replicable on Chrome and Chromium-based browsers, on Windows 10.
• Testing the scenario on Firefox(Windows 10), the issue cannot be reproduced.

To Reproduce
Steps to reproduce the behavior:

1. Open this StackBlitz example on Windows and Chrome/Chromium-based browser
2. Focus a cell in the first column of the Grid
3. Press and hold the right keyboard arrow

Expected behavior
The movement of focus inside the Grid should be smooth and visible

Describe the bug
When expanding/collapsing grouped data in the Grid re-renders all Grid rows while only the collapsed ones should be re-rendered.

To Reproduce

1. Open this CodeSandbox
2. Collapse a group
3. Open the browser's console and see that row-render has been called 1000 times

Expected behavior
The row-render method should be called for the rows that hold the collapsed data, not for all Grid rows.

In the jQuery version of the Grid, the columnMenu can be configured to show/hide the different column menu options.

Here is an example of how the sortable prop can be configured in a way the sorting options will be hidden in the column menu. 

Please provide the same configurations options for the column menu in the Native Grid

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

https://stackblitz.com/edit/mzrap6-afgvuk?file=src%2Fmain.vue

reorder the second column
result the innderHTML is NOT visible

Expected behavior
result the innderHTML is visible

workaround: use inner array instead of innerHTML - https://stackblitz.com/edit/mzrap6-y35krb?file=src%2Fmain.vue

Currently, the value of the TimePicker component can be changed by updating the values of the lists in the popup of the component and then pressing the "Set" button inside it. 

Can you provide the option to configure the component to automatically updates its value when a value in the lists inside the popup is changed? With this option, the functionality of the "Set" button won't be needed.