The Data Grid does not work properly with large datasets. In the example below with one million records, it is impossible to scroll to the bottom of the grid.

Firefox: Rows fail to render after scrolling past approximately 200,000 rows.

Chrome: Rows do render, but the skip parameter never exceeds 745,645 even when the scrollbar is at the bottom, preventing access to the remaining ~254,000 records.

This contradicts the documentation's claim that the grid "scales from hundreds to millions of records while maintaining a responsive user experience."

 

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

Please see the example - https://codesandbox.io/p/sandbox/silly-wind-tpfg8n

When column "Unit Price" is locked, while moving the horizontal scroll bar, the group header is sticky (expected behavior), but the group footer is not sticky (wrong behavior).

When using KendoReact Grid with multiple grouping levels, the Grid automatically adds horizontal indentation inside <td> elements to represent group hierarchy.

While this behavior is expected, there is no public API to control, customize, or disable this indentation.
As grouping depth increases, this extra space causes layout issues, unexpected horizontal overflow, and breaks strict or custom design systems.

Is there a reason why this spacing is not configurable?
Are there plans to expose an official option (e.g. groupIndent / groupPadding) or any supported API to manage grouped row indentation?

Example:

Description

User Impact:
Screen reader users will miss important descriptive details on the pager section, making navigation unclear.
This can lead to confusion and difficulty in understanding page context or available actions.

Plan

KendoReact

Steps To Reproduce

Open the URL: https://www.telerik.com/kendo-react-ui/components/grid in edge browser in windows.

'React Data Grid Overview' page will be open.

Press tab key to navigate to the pager section.

Verify whether screen reader is announcing descriptive information on the pager section in windows or not.

DateTimePicker - TRL support in case of no value - "שנה/חודש/יום" instead of "יום/חודש/שנה"  when the format is YYYY/MM/DD

 

The examples from https://www.telerik.com/kendo-react-ui/components/intl/i18n/loading-data work with cldr* packages up to version 47.0.0. The Current version 48.0.0 causes an error:

 

The Kendo Form component internally uses a FormContext which is ued by FormElement and Field. However this Context is not exported in @progress/kendo-react-form

Please export this context. It would really help with the usability of the Form component for complex forms. There are things in the FormContext that are not available in the formRenderProps.

Alternatively, put everything from the context into the FormRenderProps. These don't seem like they needed to be 2 different objects.

Specifically with the Context you can see what fields have been `touched`, `visited` and `modified`. But with the render props you only get a boolean if any field has been touched, visited or modified; not the names of the fields.

Be able to to modify the cut-off point depending on what baseUnit is selected in a chart time series.

e.g.

Given the following data points:

Data = [

  Friday 10th Oct: 123,

  Saturday 11th Oct: 54,

  Sunday 12th Oct: 77,

  …,

  Tuesday 20th January: 10,

]

If baseUnit = year

Currently what happens is:

1st Jan -> 1st Jan -> 1st Jan

What we want:

10th Oct -> 10th Oct -> 10th Oct

If baseUnit = month

Currently what happens is:

1st Oct -> 1st Nov -> 1st Dec

What we want:

10th Oct -> 10th Nov -> 10th Dec -> etc

*Edge case of 29th, 30th, and 31st:

Default to last day of the month

Oct 31st -> Nov 30th -> Dec 31st

If baseUnit = week

Currently what happens is:

Sunday 5th Oct -> Sunday 12th Oct -> Sunday 19th Oct

What we want:

Friday 10th Oct -> Friday 17th Oct -> Friday 24th Oct -> etc

If baseUnit = day

This is our minimum unit so everything works

In our software we want to create a filter with MultiSelectTree. The hierarchy is this: LV1 -> LV2 -> LV3. In the database the data is assigned to LV3. If the component is loaded with lot of LV3 items then selecting the parent LV2 node will result a very long tag list in the textbox part of the MultiSelectTree which is not user friendly. In this case I expect selecting the LV2 node will check the LV3 subnodes also but the textbox part has only that LV2 tag as selected. So the checkboxes should remain the same textbox should display the selected parent only.

Other cases:

- when LV1 is selected, then every children will be checked but textbox should display only the selected location

- when 99 of 100 LV3 items are checked then LV2 parent is not fully checked so textbox should display only the bins but only the first N items then use ... characters.

We use "@progress/kendo-react-treelist": "^5.10.1" in our project. Trees are usually placed in flexible containers, and users can reduce their size to 0. At this point, we get an error when calling the tableRowsVirtualization function. I have attached a screenshot at the moment of debugging. You can see that the values of items[0] and lastItem are undefined when the container size approaches 0. I didn't prepare an example to reproduce the error, because I think it's pretty clear that an error occurs here. So the questions are: if this is a bug, is it fixed in the new versions of the package? If there is a possible error on our part or it has not been fixed in the new versions, then what should we do to solve the problem? Thanks

With the ArcGauge component, when you set the rangeLineCap to something other than 'butt' (ie:  round or square), the indicator does not line up with the tick lines.  This leads to misleading values.  Please look at this StackBlitz:

 

https://stackblitz.com/edit/react-itztql

 

This will show the comparison between round and butt rangeLineCaps. 

From the screenshot as well, the ArcGauge on the right looks like the value is greater than 0, resulting in the user being mislead on the result.

We are using a customized ChartToolTip with button in our bar chart. However the tab order is not correct for multiple charts. The expect behavior we were told by our accessibility testing team is first chart -> button on tooltip -> second chart -> button on tooltip and so on. The actual behavior is tab shortcut will switch between charts then back to the first chart tooltip element. 

Hi! 

I have noticed that keyboard navigation doesn't work in the filter editor components inside the Filter component

Reproduction:

1. Open https://stackblitz.com/edit/react-rvwjsm?file=index.html
2. Choose "name" or "price" from the first dropdown
3. Type anything in the input field
4. Try to change the cursor position in the field using arrow keys - doesn't work

 Is there a way to enable it or go around it? 

It would be great if there was an animationClass prop that will make styling easier.

Hi,

The first render of a DatePicker component with an onOpen prop throws an error: Unknown event handler property `onOpen`. It will be ignored.

Reproduction:

1. Open https://stackblitz.com/edit/react-xje2zdjc?file=app%2Fapp.tsx

2. The error will appear in the console

Expected behavior:

No errors in the console

I am using KendoReact 10.2 and I am getting several warnings about deprecated Sass methods and syntax including one that is causing an error in the browser and blocks rendering. I used the sass-migrator to try to migrate these methods.

Please upgrade KendoReact so it can work with the latest Vite, React and scss/sass packages without deprecation warnings and errors.
Also fix the React version dropdown in this feedback form. It doesn't show React 19 as an option.

Provide a set of utility functions for safely creating, traversing, updating, and deleting filters inside nested CompositeFilterDescriptor trees.

It would be great if there was a way to customize the flag of the Timeline component

It would be beneficial if there was a mechanism to identify the actual grouping level of each header cell regardless of expansion state, such as exposing a groupLevel property

*** Support ticket created by Telerik by Progress staff ***
*** Please follow-up with additional details, if necessary. Thank you. ***

I want to achieve an improved customization over the font styling of the title and subtitle pieces using the SCSS theme variables. We want to globalize the style changes via SCSS