The `WorkWeekView` and `DayView` components only support displaying a continuous range of days, defined by `workWeekStart` and `workWeekEnd` (or `numberOfDays`). There is no way to specify an arbitrary set of non-consecutive weekdays (e.g., Monday, Wednesday, and Saturday) and render them as side-by-side columns in a single view.

Customers who operate on non-standard schedules — such as shift workers, part-time staff, or businesses with non-traditional work weeks — cannot represent their schedule accurately in the Scheduler without resorting to CSS workarounds that break event positioning.

Introduce a `days` prop (or equivalent) on `WorkWeekView` and `DayView` that accepts an array of `Day` enum values. When provided, the view should render only the specified days as columns, in the declared order, regardless of whether they are consecutive.

<WorkWeekView days={[Day.Monday, Day.Wednesday, Day.Saturday]} />

When filterable={true} is set, the filter input field does not respond to Home and End keys. The keys are swallowed and never reach the input element, making cursor navigation less convenient.

Steps to Reproduce:
- Render a DropDownList with filterable={true}
- Open the dropdown and type a string into the filter input
- Press Home, End, Shift+Home, or Shift+End

Expected: cursor moves to start/end of input; Shift+Home/Shift+End selects text
Actual: nothing happens in the input field

https://www.telerik.com/kendo-react-ui/components/dropdowns/dropdownlist/filtering

Problem:

Currently, passing props directly through customSlot and customItem triggers numerous unnecessary component rerenders. To mitigate this, official support recommends passing props via React Context and wrapping customSlot/customItem in React.memo, while explicitly specifying which props should trigger a rerender upon changing. These additional workarounds introduce a poor developer experience. It is initially unclear what needs to be implemented, and it introduces a high maintenance overhead, as any future component extensions or changes require manual monitoring to prevent regressions.

Proposal:

Please optimize the internal mechanics of customSlot/customItem so that they handle updates efficiently out of the box, eliminating the need for this boilerplate code. Below is an example that implements all the current recommended workarounds to avoid unnecessary redraws:

https://stackblitz.com/edit/react-kr5cmxga-dp96seni?file=app%2FcustomSlot.tsx 

Overview:

The KendoReact PDF Viewer renders every page of a document up front. For large PDFs this causes long initial load times and high memory use.

Expose load-on-demand / virtualized page rendering in the React component, matching the existing Kendo UI for Angular PDF Viewer which has:

• loadOnDemand - render pages as the user scrolls
• loadOnDemandPageSize - pages fetched/rendered per batch
  

Reference: https://www.telerik.com/kendo-angular-ui/components/pdfviewer/load-on-demand

This is a framework-parity gap. The same underlying rendering engine already supports on-demand loading in Angular (and virtualization has been requested for Blazor: httpzor/1594054-pdf-viewer-virtualization). React usershitting large documents currently have no first-party option and must swap to a third-party viewer.

Environment: @progress/kendo-react-pdf-viewer 10.2.0, React 19, Next.js 15.

ExcelExport has a prop for 'creator'. When the excel file is generated, "creator"'s value is reflected in the file's metadata

For accessibility / screen reader purposes, Title (under Description) must also be populated. Please allow a "title" prop to be accepted by the ExcelExport component.

I would like to request a new Kendo React Grid column editing option so that users can navigate editable columns using the keyboard. This feature should be similar to "navigatable" option from Kendo jQuery grid example - https://demos.telerik.com/kendo-ui/grid/editing

Thanks.

Hi, 

I'm in need of the dropdown feature in spreadsheet cells. I had been using the Kendo Spreadsheet React Wrapper which had the dropdown feature but since the latest update to Kendo React Spreadsheet I have been facing issues. Please try to get this feature as soon as possible and I'm sure this will be helpful for other users, too.

Thank you.

Hi Team,

I want to use annotations and marking in PDF and my tech stack is React is this possible with telerik currently?

Hello,

We are currently developing an application based on Kendo React components.
We are wondering if the React-Gantt chart has the functionality to edit the data by drag-n-drop the same way it possible with JQuery-Gantt (see attachment).

Thanks in advance for your help.

Kind regards,
Sergei

When implementing a custom filter cell (e.g., to support DatePicker modes such as time-only, date-only, or datetime), there is currently no straightforward way to reuse the built-in filter UI elements like the operator selector and clear button.

At the moment, these controls must be recreated manually to match the behavior and styling of the default Grid filter cells. While GridCustomFilterCellProps.children does include these elements, they are bundled together with the default filter input, making it difficult to extract and reuse only the needed parts.

It would be very helpful if the default operator dropdown and clear button were exposed separately (or made easily accessible), so they can be reused in custom filter cells.

This would:

• Ensure visual and behavioral consistency with built-in filter cells

• Reduce duplication of logic and styling

• Minimize the risk of breaking changes when internal class names or implementations are updated

A supported way to access or compose these default controls would greatly improve the developer experience when building custom filter cells.

Add an optional row-based keyboard navigation mode for the KendoReact Grid where Arrow Up and Arrow Down move focus between entire rows instead of individual cells.