When the listbox has many items (roughly 200 and growing) the item attribute makes the listbox act slow when you want to click the item.
Even if the item render only returns the same value as not setting the item attribute. It seems like all the items re-render when it gets clicked?

Also in this example https://www.telerik.com/kendo-react-ui/components/listbox/customization/ it is possible to drag and drop a custom item.
But this is not working when we copy exactly the same code from the example. The drag event gets triggered but nothing happens. 
Both lists have items to avoid this bug: https://github.com/telerik/kendo-react/issues/1300

I can post my source code but it is literally the same as the example. When we remove the item attribute the drag and drop works again. 

It would be useful to add the `title` prop to the `Button` and `Chip` components. So that we get extra information in the default browser tooltip or use the `Tooltip` component for a customized look.

Add `layout` prop (https://www.telerik.com/kendo-react-ui/components/dialogs/api/DialogActionsBarProps/#toc-layout/) to `PopoverActionsBar`.

Currently, the category value in the tooltip does not display the formatted value and the only option for changing this is by using the "render" and defining custom rendering. The formatted value should be used by default.

Not only would I like control over the group order (like from this thread https://feedback.telerik.com/kendo-react-ui/1523636-need-to-be-able-to-have-more-control-over-the-order-of-groups-in-the-kendo-grid-sort-on-the-text-is-insufficient), it would be awesome if we could sort groups themselves.

I understand that the current set up sorts children within groups but not the groups themselves. However, sorting within and between groups is a bit more intuitive to the user when they see visually-grouped information and try to sort on it => most of our users expect the groups to get sorted as well.

Although I can write my own sorting functionality, it can get out of hand quickly with ascending/descending, numeric vs alphabetic columns, and multi-sort vs single sort, but KendoReact already has the capability to sort in these three ways with its non-grouped grid functionality.

I am trying to get the DOM element of a `Popover` via`ref`, but the returned `PopoverHandle` does not expose an `element` prop. (https://www.telerik.com/kendo-react-ui/components/tooltip/api/PopoverHandle/)

Please can you keep the all component handle API consistent by always exposing the underlaying DOM element?

How to get a selected object for AutoComplete's onChange(...)?

<AutoComplete data={[{id:10, name:"test"}]} textField="name"/>

Hello,

is it possible to do reorder/drag and grop grid rows with the keyboard? It doesn't look this is set up but I wanted to check if it is (or if it's something you will be adding at some point).

https://www.telerik.com/kendo-react-ui/components/grid/rows/row-reordering/#toc-kendoreact-dragdrop

Thanks,

Rebecca

Allow the Grid to update its data without remounting the whole component, so the current selection of the filtering menu would be persisted.

We have scenarios where the data is constantly updating the filter selection is lost if the Grid is updated before pressing the `Filter` button.

Hi,

I would like to request a feature for the Kendo React Chart Zoomable feature to be able to set a zoom level. 
For example, an exposed API function to set graph's current zoom level to exactly 50% or 25% that I can use with a button maybe.

Currently the API only supports setting "zoom rate", but I would like a set Zoom function, so maybe I can save the current zoom level upon load of the chart again.

Thanks!

Hi,

Please see the following example of the Upload component being used to transfer a single file to a byte array:

https://stackblitz.com/edit/react-u2kbu9?file=app/main.tsx

Notice that all packages are latest including react 18 but I have not switched to the new createRoot API, and as per react documentation "Until you switch to the new API, your app will behave as if it’s running React 17" - this warning can be seen in the console window. When you upload a file, the FileReader onprogress and onload events result in the file being successfully uploaded with 100% progress. You can see current state and new state of all events in the console window.

Now please see the exact same example but switched to the new createRoot API:

https://stackblitz.com/edit/react-y8fuya?file=app%2Fmain.tsx

Notice that the warning is no longer visible in the console window. When you upload a file, the FileReader onprogress and onload events result in the file being successfully uploaded but the file progress is overwritten. You can see current state and new state of all events in the console window - the new state from the onProgress event is lost, and the new state in the onStatusChange event reports zero progress.

I believe this is because of automatic batching in React 18.

Kind regards,

David

1) Drag a window to a tabstrip and drop the window on the tab area.
2) The window should dock into the tabstrip as extra tab.

Hi,

Can We have an admin Dashboard for KendoReact? which has some ready components Like NavBar on top and Left, Dark and Light mode, RTL, and LTR Layouts and Forms with all input Components

I Have More projects in this React MUI Admin Dashboard and now it's very hard for me to use the KendoReact Components here.

if we Have KendoReact Admin Dashboard like that it will be easy to use KendoReact components there.

Thanks

Hello,

There is a very serious bug in the Kendo React date picker component: the month of January is simply not displayed

The issue can be witnessed on your demo page:

https://www.telerik.com/kendo-react-ui/components/dateinputs/datepicker/

Just open the picker and you'll see January is not there

https://stackblitz.com/edit/react-haejnu?file=app%2Fmain.tsx%3AL115

It is a common use case to provide Grid's dataItemKey property to make sure changes are properly reflected per documentation - https://www.telerik.com/kendo-react-ui/components/grid/api/GridProps/#toc-dataitemkey

However, when this accessor property is provided (usually a unique ID on all groups and items), Kendo uses it instead of its default auto-incremented `'ai' + absoluteIndex` key to index the <GridRow /> for each group's header and footer - giving them the same value and causing React to throw multiple warning about duplicate keys. This makes it unreliable to specify dataItemKey property when using the grouping feature with aggregate footers as it messes up with React's reconciliation mechanism.

How to reproduce (video attached):

1) open combobox
2) scroll to end of the item list
3) select last item 4999
4) open combobox again

Expected behavior: I would like to see the item list.

Actual behavoir: I see white area.

https://www.telerik.com/kendo-react-ui/components/dropdowns/combobox/virtualization/#toc-basic-configuration
https://www.telerik.com/kendo-react-ui/components/dropdowns/multiselect/virtualization/#toc-basic-configuration 
https://www.telerik.com/kendo-react-ui/components/dropdowns/dropdownlist/virtualization/#toc-basic-configuration 

is that possible to change the background line (grid )

how can I change the color of the grid or invisible in the kendo UI chart

I am using KendoReact Draggable and Droppable and we find a bug when using it. This bug even happen in the official demo.

The bug is described below:

When a droppable area is rendered out of the originall window size, the droppable cannot detect the onDragEnter() & onDropLeave(), of course onDrop neither.

it seems that kendo did not handle when user scroll while dragging the draggables, so that when the draggables was dragged to a zone out of the original window size, it failed to detect it.(Figure4)

I have also found another bug which is when you drag the draggables and scroll, the draggable will somehow detacted with the cursor, but I somehow already fixed it. Maybe it gives some hint for you to fix this bug, maybe.